Passage Data — cited environmental limits

Fetch one document by id

fetch

Read-onlyIdempotent

One document search returned, as text: limits// = every cited row for that parameter there (value, unit, statistic, conditions, and each row's instrument, edition, section or page, quoted text and source URL), and limits/// the rows of that medium alone; species/[/] = what each species register says about it, and each register searched that is silent; place/ = the instruments and parameters held there; source/ = one instrument's edition and source; permit/ = one US NPDES permit's limits by outfall. url is the page to cite; metadata.json the same rows as JSON.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	An id from search: limits/CA-QC/copper, species/Myotis lucifugus/CA-ON, place/US-OH, source/ca_mdmer, permit/PA0228061.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description does add that content is returned as text and that `url`/`metadata.json` variants exist, but it says nothing about size, truncation, or what happens on an unknown id.

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

Conciseness2/5

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

The content is a single dense run-on sentence with semicolon-separated clauses and no line breaks, making it hard to scan. The most important fact (what this tool does) is buried inside a return-value description rather than front-loaded.

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?

An output schema exists so return values needn't be explained, and annotations carry the safety profile; for a single-id fetch tool the id taxonomy is the key missing piece and it is supplied. It stops short of describing failure modes or size limits, but it is broadly complete.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description genuinely enriches the schema by mapping each id namespace (limits/, species/, place/, source/, permit/) to the specific content it resolves to, plus the medium-level variant. That is real meaning beyond the schema's terse examples.

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?

The description conveys that this retrieves a single document by id and returns it as text, and the id catalog implies the 'one document' granularity. However the opening phrase 'One document search returned, as text' is grammatically muddled and it never explicitly separates itself from siblings like search (which produces the ids) or get_permit/cite_document, which plausibly overlap.

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?

The schema hints ids come 'from search', and the description enumerates which id forms exist, implying you call this after a search. But there is no explicit when-to-use/when-not statement, no mention of alternatives, and no guidance on choosing between fetch and get_permit or cite_document for permit/citation data.

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

All Passage Data — cited environmental limits 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.