Skip to main content
Glama

verify_page

Read-onlyIdempotent

Pre-publish lint (tags, assets, layout, SEO, speed and accessibility). Summary first: health issues grouped by code, each with fix:{tool,args,fill?} — supply the fill args, then call. health.summary counts are whole-site (groups/codes filter only issues and assets). Pair with preview_page — see get_skill('verify').

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": {
      "site": "<site>"
    },
    "name": "verify_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug, e.g. acme-studio
codesNoOnly these health codes, e.g. perf_image_heavy.
pathsNoRoutes to check; omit to verify every route on the site.
detailNosummary (default): grouped by code, clean pages counted. full: per-page lists.
groupsNoOnly these groups: speed = perf_*, a11y = a11y_*, links = link_* + content_*. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Why you're calling this (activity log).",
      -  "minLength": 1,
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • removedInput schema / properties / guestToken
      Removed value: -{
      -  "description": "Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy.",
      -  "minLength": 20,
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "context"
      -]New value: +[
      +  "site"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / groups / description
      Previous value: -"Only these groups (links = links & content). Omit for all."New value: +"Only these groups: speed = perf_*, a11y = a11y_*, links = link_* + content_*. Omit for all."
  5. Changed3 schema fields changed
    • addedInput schema / properties / codes
      Added value: +{
      +  "description": "Only these health codes, e.g. perf_image_heavy.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "summary (default): grouped by code, clean pages counted. full: per-page lists.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / groups
      Added value: +{
      +  "description": "Only these groups (links = links & content). Omit for all.",
      +  "items": {
      +    "enum": [
      +      "seo",
      +      "speed",
      +      "a11y",
      +      "links"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely non-obvious behavior: summary-first output, per-issue fix:{tool,args,fill?} objects, and the caveat that health.summary counts are whole-site while groups/codes filter only issues and assets. It omits cost/latency expectations for the speed checks and any permission prerequisites for the site.

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

Conciseness4/5

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

Content is front-loaded with the purpose, then output shape, then caveats and pairings — every sentence carries information. The fix:{tool,args,fill?} notation and the "supply the fill args, then call" clause are compressed to the point of being slightly cryptic on first read.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining returns and does so at the right altitude (summary vs full, grouped-by-code issues, fix payloads, whole-site counts). It leaves the exact fix-arg contract to the referenced get_skill('verify') doc, which is a reasonable delegation but a small completeness gap.

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 100%, so the baseline is 3, but the description adds real semantics beyond the schema: that groups/codes are pure filters over issues and assets and that the returned summary counts remain whole-site. The fix/fill mechanism it describes is a caller workflow that the schema does not convey at all.

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

Purpose5/5

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

"Pre-publish lint" names a specific verb and timing, and the parenthetical enumerates exactly what is checked (tags, assets, layout, SEO, speed, accessibility). It also identifies the complementary sibling (preview_page), so an agent can place it without opening another schema.

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

Usage Guidelines4/5

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

The description establishes the usage context (pre-publish) and explicitly names preview_page as the pairing tool plus get_skill('verify') for deeper guidance. It does not state when not to use it (e.g. during drafting) or that speed checks are the slow path, so it stops short of full when/when-not coverage.

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