Passage Data — cited environmental limits

Search cited limits, species registers and permits

search

Read-onlyIdempotent

Search everything this server holds by free text: a substance and a place (copper effluent Québec, ammonia Ohio, a CAS number), a species and a place (Myotis lucifugus Ontario, little brown myotis), an instrument's title (Metal and Diamond Mining Effluent Regulations, 40 CFR 423) or a US NPDES permit number. The query is read by exact matches against what is held — a place's ISO code or name, a parameter name as a regulation prints it, a scientific name or a common name a register prints — never guessed. Each result is an id to pass to fetch, a title saying what it holds, and the url of the page with the same rows, to cite. searched says how the query was read and what was read but is not held.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Free text: a substance or measure and a place, a species and a place, an instrument's title, or an NPDES permit number.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds substantive behavioral detail: matching is exact and never guessed, query interpretation is exposed via the searched field, and each result carries an id, title, and citable url. This is rich context beyond the structured hints.

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?

The purpose is front-loaded, and the paragraph moves efficiently from scope to examples to matching behavior to return shape. It is dense but every clause contributes; it could be marginally tightened but wastes no space.

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?

Given a single required parameter, rich annotations, and an output schema, the description is complete: it explains what can be searched, how queries are interpreted, and what each result contains. Nothing an agent needs to call it correctly is missing.

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 for the single query parameter is 100%, so the baseline is 3. The description still adds meaning by giving concrete example queries and clarifying that matching is exact against held ISO codes, register names, and regulation-printed parameter names, which helps an agent formulate a valid query.

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?

The first sentence states a specific verb (Search) and scope (everything this server holds, by free text), and the examples enumerate the resource types. It also positions the result as an id to pass to fetch, which distinguishes it from the retrieval sibling without ambiguity.

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?

The description gives clear context for when this tool is appropriate by listing the kinds of free-text queries it accepts (substance and place, species and place, instrument title, permit number). It does not, however, explicitly name alternatives like find_limits or find_designations or state when not to use it, so no exclusions are offered.

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.