Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

eis-reports

GET https://ticks.bnm.farm/eis-reports — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. EPA NEPA Environmental Impact Statement PDFs GET ?id= is one official text ($0.02). Newest chunk on a plain GET ($0.05); older chunk if they ask (?before, $0.05); newer than a watermark ?since= ($0.05). Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOfficial catalog id. That one official text, $0.02. Same door, not a new SKU.
pageNo1-based page. Page 1 is the newest chunk. Ignored when since/before is set.
sinceNoISO timestamp or official catalog id. Official texts newer than this watermark, $0.05. Empty new set is 304 or recordCount 0.
beforeNoOfficial catalog id or YYYY-MM-DD. Next older chunk on the same URL, another $0.05. Omit for the newest chunk.
x_paymentNoOptional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"1-based page. Page 1 is the newest chunk. Ignored when before is set."New value: +"1-based page. Page 1 is the newest chunk. Ignored when since/before is set."
    • addedInput schema / properties / since
      Added value: +{
+  "description": "ISO timestamp or official catalog id. Official texts newer than this watermark, $0.05. Empty new set is 304 or recordCount 0.",
+  "type": "string"
+}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behaviors: payment requirement, HTTP 402 when unpaid, JSON response after valid X-PAYMENT, and chunk/pagination semantics. It could also mention rate limits or result shape, but the core behavioral traits are well covered.

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 description is a single dense block that opens with a URL and payment address, which is not agent-relevant for tool selection. Key info is present, but the 'Not a new SKU' line and scattered pricing make it poorly structured and not 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?

For a payment-gated API with chunked retrieval, the description covers the essential operational details: pricing per mode, the 402 behavior, the X-PAYMENT flow, and the JSON return. It does not describe the response shape, but no output schema exists and the provided schema is rich enough to guide invocation.

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 description coverage is 100%, so the baseline is 3. The description repeats most parameter semantics already in the schema (id, since, before, page) and adds pricing context, but does not add substantial new meaning beyond what the schema provides.

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 clearly identifies the resource as 'EPA NEPA Environmental Impact Statement PDFs' and specifies the GET endpoint and retrieval modes (by id, newest chunk, older/newer chunks). It is not a tautology and the resource type distinguishes it from sibling report tools, though the purpose is buried among payment details.

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 provides clear context for when to use this tool: it is for EPA NEPA EIS PDFs and explains when to use plain GET vs ?id vs ?before vs ?since. It does not explicitly name alternatives or exclusions, but the domain-specific wording makes the intended use clear.

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

All BNM Data Shop 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