get-flowie.com WebMCP audit

Rescan
audited Aug 28, 2026in 4s
48/ 100

3 tools registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use66
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
flowie_search: fail

flowie_search

Search public get-flowie.com content (platform, solutions, e-invoicing country coverage, integrations, pricing, blog, glossary) and return the most relevant pages with title, URL and a snippet.Takes an action on the site.
pagehttps://get-flowie.com/
implementation
viaimperative
entry pointdocument
registered after293ms
executepresent
api surface
queryrequired
limitoptional
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
4 findings
warningSchema quality
2.7 / 4
1 of 3 tool schemas are harder for an agent to use than they need to be: flowie_search 1 parameter has no description (limit).
flowie_search: 1 parameter has no description (limit)
fix
{
  name: "flowie_search",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 3 names do not start with a verb (flowie_search).
fix
{ name: "flowie_search" /* short, unique, verb-based */ }
failAnnotations present
0 / 4
3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
flowie_search, flowie_overview, flowie_read_page
fix
{
  name: "flowie_search",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
3 of 3 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
flowie_search, flowie_overview, flowie_read_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="flowie_search" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "flowie_search",
  "description": "Search public get-flowie.com content (platform, solutions, e-invoicing country coverage, integrations, pricing, blog, glossary) and return the most relevant pages with title, URL and a snippet.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Natural-language query, e.g. 'France e-invoicing mandate' or 'SAP integration'."
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 10,
        "default": 5
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}
Showing flowie_search

Findings

WebMCP use

66 / 100 · weight 50
passTools registered
4 / 4
3 tools registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither.
passRegistration timing
4 / 4
Every measured tool registered within 293.59999990463257ms of navigation.
toolflowie_read_page
passCanonical entry point
4 / 4
All 3 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 3 tools declare a structurally valid object input schema.
warningSchema quality
2.7 / 4
1 of 3 tool schemas are harder for an agent to use than they need to be: flowie_search 1 parameter has no description (limit).
toolflowie_search
flowie_search: 1 parameter has no description (limit)
fix
{
  name: "flowie_search",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 3 tools declare an execute handler.
failAnnotations present
0 / 4
3 of 3 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolflowie_search
flowie_search, flowie_overview, flowie_read_page
fix
{
  name: "flowie_search",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
not applicableAnnotation mismatch
0 / 3
No tool declares a readOnlyHint, so there is no safety claim to contradict.
not applicableUntrusted content hint
0 / 2
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
3 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

50 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 3 names do not start with a verb (flowie_search).
toolflowie_search
fix
{ name: "flowie_search" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
not applicableCoverage vs. site type
0 / 8
This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
3 of 3 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolflowie_search
flowie_search, flowie_overview, flowie_read_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="flowie_search" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
3
run time
4s
finished
Aug 28, 2026