Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

superfund-rods

GET https://ticks.bnm.farm/superfund-rods — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. EPA Superfund ROD and Five-Year Review text 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. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"1-based page. Page 1 is the newest chunk. Ignored when since/before is set."New value: +"1-based page. Page 1 is the newest chunk. Ignored when before is set."
    • removedInput schema / properties / since
      Removed 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"
-}
  3. 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"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: payment requirement (HTTP 402 when unpaid), behavior after valid X-PAYMENT (returns JSON), pagination semantics (newest chunk, older chunks, watermark), and pricing tiers. It also notes 'Not a new SKU' to clarify scope.

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 description is a single dense paragraph that front-loads the URL and core pricing. It uses semicolons to separate clauses, which is efficient but could be broken into bullet points for readability. Every sentence carries information about usage or behavior.

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?

Without an output schema, the description explains that a successful paid request returns JSON but does not detail the JSON structure. It covers payment, pagination, and error behavior (402), and the parameter descriptions cover edge cases like empty sets (304/recordCount 0). Overall, it is complete for making a call, though return format details are 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 covers 100% of parameters with descriptions, so baseline is 3. The tool description adds pricing per parameter and clarifies interactions (e.g., 'Ignored when since/before is set'), providing meaningful extra semantics beyond the schema.

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 explicitly states it is a GET endpoint for EPA Superfund ROD and Five-Year Review text, with a clear URL and pricing model. It distinguishes its core function from generic siblings by specifying the exact resource type and pagination behavior.

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 description explains how to use parameters (id, before, since) and payment mechanics, but does not explicitly contrast with sibling tools like get-one or get-page. It implies usage context for pagination but lacks explicit 'use this when' guidance relative to alternatives.

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