Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

ticks

GET https://ticks.bnm.farm/ticks — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. USDA farm market prices Whole current table ($0.05). Send If-None-Match or ?since= to 304 an unchanged snapshot. Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoISO timestamp or asOf date. 304 when the current table is not newer.
x_paymentNoOptional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header.
if_none_matchNoETag from a prior paid GET. Unchanged snapshot returns HTTP 304 and is not re-sold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / if_none_match
      Added value: +{
+  "description": "ETag from a prior paid GET. Unchanged snapshot returns HTTP 304 and is not re-sold.",
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "ISO timestamp or asOf date. 304 when the current table is not newer.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • removedInput schema / properties / if_none_match
      Removed value: -{
-  "description": "ETag from a prior paid GET. Unchanged snapshot returns HTTP 304 and is not re-sold.",
-  "type": "string"
-}
    • removedInput schema / properties / since
      Removed value: -{
-  "description": "ISO timestamp or asOf date. 304 when the current table is not newer.",
-  "type": "string"
-}
  3. Changed2 schema fields changed
    • addedInput schema / properties / if_none_match
      Added value: +{
+  "description": "ETag from a prior paid GET. Unchanged snapshot returns HTTP 304 and is not re-sold.",
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "ISO timestamp or asOf date. 304 when the current table is not newer.",
+  "type": "string"
+}
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states the $0.05 USDC payment requirement, the payment address, HTTP 402 behavior, 304 caching semantics, and the fact that unchanged snapshots are not re-sold. This is strong behavioral transparency for a paid data endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loads the URL and cost, but several sentence fragments and the cryptic 'Not a new SKU.' reduce clarity. The information is useful, but the structuring is rough and one phrase does not earn 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 paid, conditional GET tool with no output schema, the description covers the essential operational details: cost, payment address, unpaid behavior, conditional request behavior, and successful response mode. It leaves the exact mechanics of a 'valid X-PAYMENT' and response shape unspecified, but the schema helps fill the parameter gap.

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 reinforces the caching behavior of since and if_none_match, but does not add significant meaning beyond what the input schema already documents. It also mentions X-PAYMENT only indirectly.

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 endpoint that returns 'USDA farm market prices' for the current table, with a specific URL. It does not explicitly contrast itself with sibling tools, but the resource and action are concrete enough for an agent to understand what the tool offers.

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 explains the conditions under which caching and payment apply: use If-None-Match or ?since= to get a 304 on unchanged snapshots, unpaid requests return 402, and valid X-PAYMENT unlocks JSON. It does not discuss alternatives or exclusion cases, but the usage context for this paid endpoint is reasonably 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