Skip to main content
Glama

Verify a fix

verify_fix
Read-onlyIdempotent

After changing a page: checks it again the way AI crawlers see it (fresh audit: crawler access, noindex, text without JavaScript, title, structured data, date) and, for a Kliqo action, whether real AI crawlers (verified by IP, from Crawl insights) have read the page since. Says what still fails, or that it's ready to mark done. Needs sign-in to Kliqo (read-only).

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": {
      "url": "<url>"
    },
    "name": "verify_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
projectNoProject name, domain or id; leave out for the workspace's current project
action_idNo

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds context beyond the annotations: it needs a Kliqo sign-in (read-only), it performs a fresh live audit rather than reading cached data, and the crawl evidence is IP-verified via Crawl insights. It does not discuss latency, throttling, or how fresh the crawler data window is, but the auth requirement and freshness guarantee are exactly the kind of detail annotations cannot express.

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?

Front-loaded with the triggering condition and no filler sentences; the parenthetical check list earns its length by defining scope. It is a dense single block, though, and the nested clauses and parentheses make it slower to skim than a short lead sentence plus a list would be.

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 an output schema present, the description need not explain return values, and it still summarizes the verdict ('says what still fails, or that it's ready to mark done'). Auth and the audit dimensions are covered; the only real gap is the underspecified url and action_id parameters for a three-parameter tool.

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

Parameters3/5

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

Schema coverage is only 33% — only 'project' is described — so the description must carry the load for url and action_id. 'for a Kliqo action' weakly signals action_id's purpose and 'after changing a page' implies url, but the description never states the expected URL format or what action_id actually changes in the response, leaving real ambiguity.

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?

States a specific verb and resource: re-checks a page the way AI crawlers see it, enumerating the exact checks (crawler access, noindex, no-JS text, title, structured data, date). The 'After changing a page' framing plus the conditional crawl-insights crawl check makes it distinguishable from a first-time audit or a standalone crawler listing, even though no sibling is named.

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?

'After changing a page' gives a clear temporal trigger and 'for a Kliqo action' scopes the crawl-insights part, so an agent knows when to reach for it. It does not explicitly contrast with audit_page_for_ai or check_ai_crawlers, so the agent must infer why it should use this rather than re-running the initial audit.

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