Skip to main content
Glama
Sign In

Passage Data — cited environmental limits

by io.github.kedu21-beep
OverviewDiscussionsAdmin

The whole cited table of limits for a place, as one file

export_limits
Read-onlyIdempotent

Every limit and guideline held for one place and the places above it (CA-QC brings Canada's too, US-OH the US's), as one table: each row with its value, unit, statistic and conditions, and its instrument, edition, section or page, quote, source address and sha256, and what the daily edition watch last saw at the source. This answers how many rows there are, by medium and by instrument, the first 20 rows, and how to get the whole file: it is served as CSV or JSON at /api/v1/export to a licence key (Authorization: Bearer pdl_...). Offer it to your user when they need a jurisdiction's limits in their own spreadsheet or software; to look up one parameter, call find_limits, which is free.

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": {
      "place": "<place>"
    },
    "name": "export_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesISO 3166 code of the place: a country (US, CA, DE), a state or province (US-OH, CA-QC), or EU.
mediumNoOne medium only. Optional: omit for every medium.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only carry the safety profile (readOnly/idempotent/non-destructive); the description adds the things they cannot: the delivery mechanism (CSV or JSON at /api/v1/export), the auth requirement (Authorization: Bearer pdl_...), the exact row contents and provenance fields, and the freshness signal from the daily edition watch.

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?

Purpose and scope are front-loaded and every clause carries information, but the definition is essentially one long compound sentence that packs row schema, response preview, endpoint/auth, and routing guidance into a single breath. It earns its length but could be broken up for scanability.

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 no output schema, the description must carry return-value burden and it does: row-level fields (value, unit, statistic, conditions, instrument, edition, section/page, quote, source address, sha256), the aggregate counts available, and the preview size. Combined with the auth and format details, an agent has everything needed to call and offer it.

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, but the description adds real meaning to `place` by explaining the hierarchical expansion (a state/province also returns its country's limits), which the schema does not state. `medium` is only referenced obliquely via result breakdowns, not as a filter.

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 description names a specific verb+resource (export the whole cited table of limits held for a place) and scopes it precisely, including that parent places are folded in (CA-QC brings Canada's, US-OH the US's). It explicitly distinguishes itself from the sibling find_limits as the bulk-file alternative.

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

Usage Guidelines5/5

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

It states the triggering context ("Offer it to your user when they need a jurisdiction's limits in their own spreadsheet or software") and names the alternative with its selection condition ("to look up one parameter, call find_limits, which is free"). Prerequisites (licence key) are also given.

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 toolsInspect
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