Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

fifra-orders

GET https://ticks.bnm.farm/fifra-orders — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. EPA FIFRA institution order / consent 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

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and discloses a lot: monetized access ($0.05/$0.02 USDC on Base to a specific address), HTTP 402 when unpaid, JSON returned after a valid X-PAYMENT, chunk/page/watermark behavior, and 'Not a new SKU' clarifying the shared payment door. It does not describe the JSON shape, but for a read-only GET the payment and error profile is unusually 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.

Conciseness4/5

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

Three sentences with no filler, and the URL and price are front-loaded for quick recognition. The first sentence is overly dense — it crams the payment address, price, resource type, and a sub-pricing rule into one long clause — but every clause earns its place.

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 monetized, paginated, watermark-based tool with five optional parameters, no annotations, and no output schema, the description covers purpose, per-parameter pricing, payment flow, error behavior, and chunk semantics — far more than the typical sibling. The notable gaps are the JSON return shape and explicit sibling-routing guidance, but an agent can call and pay for this endpoint correctly based on the text alone.

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% with already-rich parameter descriptions (pricing embedded in id, 304/recordCount 0 semantics in since), so the baseline is 3. The description adds value by explaining the economics of the chunk model — newest chunk $0.05, older via ?before $0.05, watermark via ?since $0.05 — which helps an agent decide which parameter to set for a given retrieval need.

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 identifies the resource ('EPA FIFRA institution order / consent text') and the verb/URL (GET https://ticks.bnm.farm/fifra-orders), which distinguishes it from the 50+ sibling regulatory-document tools by agency and document type. However, the purpose statement is buried among payment mechanics — the opening sentence leads with the USDC price and wallet address rather than what the tool fetches.

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 gives a clear operational usage model: plain GET for the newest chunk, ?before for older chunks, ?since for newer-than-watermark, and ?id for a single official text. It never explicitly names an alternative tool or states when to prefer fifra-orders over a sibling, so cross-tool selection relies on the agent inferring from the name.

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