Skip to main content
Glama

ProofFetch — Cited Web Evidence

Check a public page (free)

proof_fetch_preflight
Read-onlyIdempotent

Free: checks a public URL and returns fetchability, provenance, hashes, deterministic injection indicators and a free preview of the first 1,000 or so characters of text (short pages come back whole); not a safety guarantee. No payment or purchase. Example: {"url":"https://example.com/","maxChars":30000}.

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_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired: the address of one public web page or PDF, for example https://example.com/; a bare domain such as example.com also works. Not a search phrase or placeholder. No credentials, private networks, authenticated pages or browser rendering.
imagesNoWith markdown: keep images as ![alt](src) (true, the default) or leave them out.
formatsNoOptional. With markdown, the free check also returns markdownPreview: the start of the clean Markdown, cut at the same size as the text preview. Links, metadata and extract come with a full extraction.
maxCharsNoMaximum normalized characters to extract. Free preflight returns metadata plus a preview of about the first 1,000 characters.
removeSelectorNoWith markdown: drop the parts of the page matching this CSS selector before reading, for example ".ads, .comments".
targetSelectorNoWith markdown: read only the parts of the page matching this CSS selector, for example "article" or "#pricing".
onlyMainContentNoWith markdown: leave out menus, headers, footers, cookie notices and sidebars (true, the default) or keep the whole page (false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / formats
      Added value: +{
      +  "description": "Optional. With markdown, the free check also returns markdownPreview: the start of the clean Markdown, cut at the same size as the text preview. Links, metadata and extract come with a full extraction.",
      +  "examples": [
      +    [
      +      "markdown",
      +      "links"
      +    ]
      +  ],
      +  "items": {
      +    "enum": [
      +      "markdown",
      +      "links",
      +      "metadata"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / images
      Added value: +{
      +  "default": true,
      +  "description": "With markdown: keep images as ![alt](src) (true, the default) or leave them out.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / onlyMainContent
      Added value: +{
      +  "default": true,
      +  "description": "With markdown: leave out menus, headers, footers, cookie notices and sidebars (true, the default) or keep the whole page (false).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / removeSelector
      Added value: +{
      +  "description": "With markdown: drop the parts of the page matching this CSS selector before reading, for example \".ads, .comments\".",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / targetSelector
      Added value: +{
      +  "description": "With markdown: read only the parts of the page matching this CSS selector, for example \"article\" or \"#pricing\".",
      +  "maxLength": 500,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTP(S) document URL. No credentials, private networks, authenticated pages or browser rendering."New value: +"Required: the address of one public web page or PDF, for example https://example.com/; a bare domain such as example.com also works. Not a search phrase or placeholder. No credentials, private networks, authenticated pages or browser rendering."
    • removedInput schema / properties / url / format
      Removed value: -"uri"
  3. Changed1 schema field changed
    • changedInput schema / properties / maxChars / description
      Previous value: -"Maximum normalized characters to extract. Free preflight returns metadata only, never the extracted text."New value: +"Maximum normalized characters to extract. Free preflight returns metadata plus a preview of about the first 1,000 characters."
  4. Changed4 schema fields changed
    • addedInput schema / properties / maxChars / description
      Added value: +"Maximum normalized characters to extract. Free preflight returns metadata only, never the extracted text."
    • addedInput schema / properties / maxChars / examples
      Added value: +[
      +  30000
      +]
    • addedInput schema / properties / url / description
      Added value: +"Public HTTP(S) document URL. No credentials, private networks, authenticated pages or browser rendering."
    • addedInput schema / properties / url / examples
      Added value: +[
      +  "https://example.com/"
      +]
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new context: no payment required, the preview is capped at ~1,000 characters regardless of requested size, and results are "not a safety guarantee." It omits rate limits and any detail on how injection indicators should be interpreted, keeping it below a 5.

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

Conciseness5/5

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

Front-loaded with "Free:" followed by outputs, the caveat, and a compact call example – the reader gets the value proposition in the first clause. Some redundancy exists ("Free" plus "No payment or purchase"), but every part is short and informative, with no wasted paragraphs.

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?

With 7 optional-heavy parameters, no output schema, and annotations covering safety, the description supplies what's missing: what the response contains, the preview size limit, that it is not a safety verdict, and how formats interact with the free tier. An agent can decide and call correctly without further information.

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; the description earns the extra point by resolving a real ambiguity: maxChars defaults to 30000 but the free preflight still returns only ~1,000 characters, and formats only yields markdownPreview while links/metadata require full extraction. That meaning is not fully derivable from the schema alone.

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?

Names a specific verb and resource ("checks a public URL") and enumerates the returns: fetchability, provenance, hashes, injection indicators, and a capped text preview. It is clear what the tool does, but sibling differentiation is only implicit via the word "Free" rather than an explicit contrast with proof_fetch_evidence or proof_fetch_crawl.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "Free" plus "a free preview of the first 1,000 or so characters" and the note that "Links, metadata and extract come with a full extraction" hints that other tools cover the full case. There is no explicit when-to-use/when-not statement or named alternative, so the agent must infer the routing from context.

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.