Skip to main content
Glama

BNM Data Shop

by io.github.bnmbnmai
OverviewDiscussionsAdmin

import-alerts

GET https://ticks.bnm.farm/import-alerts — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. FDA Import Alerts / DWPE 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

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it states unpaid calls return HTTP 402, valid X-PAYMENT returns JSON, unchanged snapshots return 304 via If-None-Match or since, and it includes the payment address and amount. It does not describe response contents or other error cases, but the key transactional behavior is explicit.

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 dense but mostly purposeful: URL, pricing, payment destination, dataset, conditional behavior, and payment outcome are all included. The closing phrase 'Not a new SKU' is ambiguous and slightly weakens clarity, but the overall block remains compact and information-rich.

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 single-resource endpoint with no output schema and no annotations, the description covers the essential invocation context: how to pay, what happens before and after payment, and how conditional headers avoid re-billing. It could be more explicit about the JSON response shape, but an agent has enough to call and interpret the main outcomes.

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?

The input schema already documents all three parameters thoroughly, including the 304 behavior and ETag reuse. The description reinforces the conditional-request usage but adds little beyond what the schema provides, so the baseline 3 is appropriate.

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 specific resource: a paid GET endpoint returning the FDA Import Alerts / DWPE current table. It is specific about the verb, URL, and dataset, though it does not explicitly distinguish itself from the many sibling regulatory-data tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to choose this tool over alternatives like search, get-page, or other dataset-specific endpoints. The description explains the payment and conditional-request workflow, but not the decision context or exclusions.

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