Quattr

indexation_gap_diagnosis

Read-only

Which crawled pages are NOT indexable, and why? Lists URLs the crawler found that are flagged not-indexable plus the reason (noindex, canonical, robots, status) from the site crawl graph. Use for "what pages are blocked from indexing", "why isn't this page indexed", "indexation issues". Requires the site crawl feed.

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": {
      "date_range": "<date_range>"
    },
    "name": "indexation_gap_diagnosis"
  }
}

Input Schema

Name	Required	Description	Default
`top_n`	No	Max URLs to return.
`date_range`	Yes	Explicit date range, e.g. "2026-05-01 to 2026-05-31". Both endpoints are INCLUSIVE — the END day is covered (a 7-day range = 7 days). Quattr weeks run Sunday–Saturday; for "last week" use the most recent complete Sun–Sat span.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered. The description adds meaningful context beyond that: the source ('site crawl graph') and the prerequisite ('Requires the site crawl feed'), which affects whether the call can succeed.

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-loads the core question ('Which crawled pages are NOT indexable, and why?') then supplies output shape, reasons, usage triggers and the prerequisite. Every sentence carries weight, though the multiple quoted example phrases run slightly long.

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

Completeness5/5

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

For a read-only diagnostic with no output schema, the description states what is returned (URLs plus non-indexable reason), the data source, and the crawl-feed prerequisite. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, including detailed inclusive-date-range and Sun–Sat week semantics, so the schema carries parameter meaning. The description adds nothing about top_n or date_range, making the baseline 3 correct.

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+resource: lists crawled URLs flagged non-indexable and the reason (noindex, canonical, robots, status). It is clearly distinguishable from siblings like orphan_pages, crawl_budget_waste, and render_analysis, which address different crawl concerns.

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?

Gives explicit usage triggers via quoted queries ("what pages are blocked from indexing", "why isn't this page indexed", "indexation issues"), which maps agent intent to the tool. It does not name alternative sibling tools or state when NOT to use it, keeping it short of a 5.

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

All Quattr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?