Skip to main content
Glama

dom-recipe-match

Check whether a saved interaction recipe still applies to the current version of a page — Compares a recipe (ordered steps naming selectors from an earlier dom-skeleton call), the saved skeleton elements those selectors came from, and the current page HTML. Per step it reports matched (same selector, same tag, type, role and name), changed (selector still exists but the element differs), moved (the same element now has a different selector, given as newSelector), ambiguous (several cur

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recipe": "<recipe>",
      "saved": "<saved>",
      "html": "<html>"
    },
    "name": "dom-recipe-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesCurrent page HTML.
savedYeselements from an earlier dom-skeleton response.
recipeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the per-step outcome taxonomy (matched, changed, moved, ambiguous) plus the newSelector field for moved elements, which is genuine behavioral detail. However, the 'ambiguous' definition is cut off, and it never states that the call is read-only/pure analysis with no side effects or what happens on malformed selectors, leaving important behavioral traits undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded with the verification purpose before the input comparison, so there is little waste. But the description visibly ends mid-sentence ('ambiguous (several cur'), meaning one of the four reported statuses is never explained, which is a structural defect rather than brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must describe results; it partially does via the per-step status list, which is the right instinct. Missing is any statement of the overall return shape (a verdict, counts, ordering) and completion of the 'ambiguous' case, so an agent cannot fully predict the response for a 3-parameter nested-input tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates meaningfully: it defines recipe as an ordered list of steps naming selectors from an earlier dom-skeleton call, saved as the skeleton elements those selectors came from, and html as the current page HTML. That adds real semantics about the relationship between the three inputs (selectors must come from saved) that the schema alone does not express. Truncation prevents a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Check whether a saved interaction recipe still applies to the current version of a page', and names the three inputs it compares (recipe, saved skeleton elements, current page HTML). It also distinguishes itself from the sibling dom-skeleton by noting the selectors originate from an earlier dom-skeleton call. It stops short of 5 because the sentence is truncated mid-word ('ambiguous (several cur') and never cleanly closes the comparison summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool is used after a page version change to verify a saved recipe derived from an earlier dom-skeleton response. There is no explicit when-not guidance, no statement about what to do when a step is 'changed' or 'moved' (e.g. whether to re-run dom-skeleton), and no named alternative such as recipe-scale.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources