Skip to main content
Glama

ProofFetch — Cited Web Evidence

List a site's pages (free)

proof_fetch_map
Read-onlyIdempotent

Free: lists the addresses of a public site from its robots.txt sitemaps, /sitemap.xml and the links on the page given. No key, nothing extracted or charged. Use it to find the pages to fetch. Example: {"url":"https://example.com/","search":"/docs/"}.

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": "proof_fetch_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAny page on the site, usually its home page, for example https://example.com/.
limitNoHow many addresses to return.
searchNoOptional: only addresses containing this text, for example "/docs/".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description's added value is the cost/auth profile: "No key, nothing extracted or charged." It also discloses the discovery sources, which tells the agent what output to expect (addresses only, nothing extracted). It stops short of covering pagination or behavior when no sitemap exists.

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 free/cost fact, then the mechanism, then the usage, then a compact example — four short units with no filler. The "Free:" prefix is slightly promotional but does carry real cost information for an agent deciding whether to call.

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 three-parameter read tool with full schema coverage, rich annotations, and no output schema, the definition covers cost, sources, purpose, and an example. Minor gaps remain around result volume/pagination and fallback behavior when sitemaps are absent, but nothing essential to invoking 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 coverage is 100%, so url, limit, and search are already documented with defaults and bounds. The example call restates the url/search pairing without adding new semantics such as whether search is a substring match against the full address versus the path. Baseline 3 is appropriate here.

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 ("lists the addresses of a public site") and even names the discovery sources used (robots.txt sitemaps, /sitemap.xml, on-page links). It is clearly distinguishable from a fetch/crawl sibling because it only enumerates addresses. It does not name a sibling explicitly, which keeps it short of a 5.

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?

"Use it to find the pages to fetch" gives clear downstream context for when to reach for this tool rather than fetching blindly. There is no explicit exclusion or named alternative for cases like deep crawling, but the intended role in the workflow is unambiguous.

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.