fyndling.de WebMCP audit

Rescan
audited Aug 28, 2026in 5s
74/ 100

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

WebMCP use90
Usefulness86
Human experience14
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
find_events_near: warning

find_events_near

Find medieval markets, concerts, castle events, living-history events and renfaires near a geographic location, sorted by distance. Each result includes fyndling_url, the canonical event page link.Answers a question. Declared read only.
pagehttps://fyndling.de/
implementation
viaimperative
entry pointdocument
registered after248ms
executepresent
api surface
latrequired
lonrequired
radius_kmoptional
typesoptional
date_fromoptional
date_tooptional
limitoptional
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
1 finding
warningHuman parity
1.1 / 8
6 of 7 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.
find_events_near, list_events, get_event, search_recipes, get_recipe
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="find_events_near" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "find_events_near",
  "description": "Find medieval markets, concerts, castle events, living-history events and renfaires near a geographic location, sorted by distance. Each result includes fyndling_url, the canonical event page link.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "lat": {
        "type": "number",
        "description": "Latitude of the search center"
      },
      "lon": {
        "type": "number",
        "description": "Longitude of the search center"
      },
      "radius_km": {
        "type": "number",
        "description": "Search radius in km (default 50, max 500)"
      },
      "types": {
        "type": "array",
        "items": {
          "type": "string",
          "enum": [
            "market",
            "concert",
            "burg_event",
            "living_history",
            "renfaire"
          ]
        },
        "description": "Category filter. Any of: market, concert, burg_event, living_history, renfaire"
      },
      "date_from": {
        "type": "string",
        "description": "Start date ISO 8601, e.g. 2026-06-01"
      },
      "date_to": {
        "type": "string",
        "description": "End date ISO 8601, e.g. 2026-08-31"
      },
      "limit": {
        "type": "integer",
        "description": "Max results, default 20, max 100"
      }
    },
    "required": [
      "lat",
      "lon"
    ]
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing find_events_near

Findings

WebMCP use

90 / 100 · weight 50
passTools registered
4 / 4
6 imperative tools and 1 declarative form registered across 1 page.
passReal-browser eligible
8 / 8
A real browser exposes modelContext natively on this page, so the tools registered here are visible to an agent today.
passRegistration timing
4 / 4
Every measured tool registered within 248.20000004768372ms of navigation. 1 further tool carried no measurable registration time.
toollist_events
passCanonical entry point
4 / 4
All 6 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 6 tools declare a structurally valid object input schema.
warningSchema quality
2.3 / 4
3 of 7 tool schemas are harder for an agent to use than they need to be: list_events declares no required list, so an agent cannot tell which parameters are mandatory.
toollist_events
list_events: declares no required list, so an agent cannot tell which parameters are mandatory; search_recipes: 1 parameter description is over Chrome's 150-character guidance; compose_menu: 3 paramet
fix
{
  name: "list_events",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 6 tools declare an execute handler.
passAnnotations present
4 / 4
All 6 tools declare a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (6 declared hints checked).
warningUntrusted content hint
0 / 2
1 of 1 tools look like they return text written by other people but declare no untrustedContentHint, so an agent will treat the response as the site speaking.
toolreport_event
report_event: review, user
fix
{ name: "report_event", annotations: { untrustedContentHint: true } }
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
6 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

86 / 100 · weight 30
warningNaming quality
1.7 / 2
Tool naming makes selection harder than it needs to be: 2 names do not start with a verb (compose_menu).
toolcompose_menu
fix
{ name: "compose_menu" /* 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

14 / 100 · weight 20
warningHuman parity
1.1 / 8
6 of 7 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.
toolfind_events_near
find_events_near, list_events, get_event, search_recipes, get_recipe
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="find_events_near" 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
7
run time
5s
finished
Aug 28, 2026