Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

awa

GET https://ticks.bnm.farm/awa — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. USDA APHIS AWA inspection-report observation 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.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the paid nature of the API, the USDC payment address, the 402 response when unpaid, and the JSON response after a valid X-PAYMENT. It does not cover response structure or rate limits, but the most consequential behavioral traits are exposed.

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 compact and every sentence contributes pricing, access, or behavioral information, with the endpoint and payment model front-loaded. The punctuation is a bit run-on and 'GET' is repeated, but there is no filler.

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 paid external API with no output schema and no annotations, the description is fairly complete: it covers the endpoint, payment, authentication header, 402 error, JSON return, single-text id access, paging, and watermarking. It could include an example response or clearer sibling routing, but the operational contract is mostly sufficient.

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 coverage is 100%, so the baseline is 3. The description mostly restates pricing and paging behavior that also appears in the parameter descriptions, such as 'that one official text, $0.02' and 'another $0.05.' It adds little semantic meaning beyond what the schema already 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 a GET operation against a concrete URL and names the resource: USDA APHIS AWA inspection-report observation text. It explains what the tool returns (one official text by id, newest/older chunks by pagination). It does not explicitly contrast awa with sibling tools, so it stops short of full differentiation.

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 concrete usage modes: plain GET for the newest chunk, ?before for older chunks, ?since for texts newer than a watermark, and ?id for a single official text. It also explains the payment flow and the 402 failure mode. It does not provide explicit when-not-to-use guidance or alternatives among sibling tools.

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