Quattr

orphan_pages

Read-only

Which crawled pages have no internal links pointing to them? Lists URLs with zero incoming links from the crawl graph — orphans are hard for crawlers and users to reach. Use for "find orphan pages", "pages with no internal links". 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": "orphan_pages"
  }
}

Input Schema

Name	Required	Description	Default
`top_n`	No
`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/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds real context beyond them: the rationale (orphans are hard for crawlers and users to reach) and the crawl-feed dependency. It does not describe result ordering, pagination, or limits.

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 core question, then the definition, then usage and prerequisite. Nearly every sentence earns its place; the second sentence slightly restates the first, but the total size is appropriate.

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?

For a low-complexity read tool with no output schema and annotation-covered safety, the description covers purpose, rationale, usage, and the crawl-feed prerequisite. The only real gap is the unexplained top_n parameter, which matters for controlling output size.

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

Parameters2/5

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

Schema coverage is only 50% and the description compensates for none of it. It never mentions top_n (untyped-default and undocumented in the schema) nor adds meaning to date_range beyond what the schema already states in detail.

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 resource and defining condition: crawled pages with zero incoming internal links from the crawl graph. The opening question plus the clarifying sentence make the concept unambiguous, and it is distinguishable from the related sibling internal_link_flow.

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 trigger phrases ("find orphan pages", "pages with no internal links") and a precondition ("Requires the site crawl feed"). It stops short of naming an alternative tool or a when-not-to-use condition, so it is strong context without full routing.

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?