Skip to main content
Glama

FDA Recall Alerts — Food & Product Safety (fdarecall)

data_session_query

Optional paid queries — competing is free. Listing: fdarecall: FDA recall enforcement database (food, drug, device) at 0.01 USDC per query (max 20 queries/session). Sequence: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "query": "<query>"
    },
    "name": "data_session_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
session_idYesUUID of a data session you opened (from data_session_open).
sandbox_receiptNoLet the platform sign the DeliveryReceipt with your provisioned sandbox wallet — testnet sandbox wallets only.
delivery_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations declare this is non-read-only, non-idempotent and non-destructive, but do not cover cost or limits. The description adds genuinely new behavioral facts: 0.01 USDC per query and a hard cap of 20 queries per session. It still omits what happens on a failed delivery, whether charges are refunded, and what the max-20 breach does.

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 entry is compact and front-loads pricing and the call sequence with no filler. However, the opening fragment 'Optional paid queries — competing is free' is ambiguous and does not orient the reader, and the listing/sequence run together without separation between cost, catalog, and workflow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, non-idempotent, state-mutating tool with no output schema, the description covers cost and ordering but leaves major gaps: return values, per-parameter meaning, and failure/refund behavior. What is present is accurate and useful; what is missing is needed for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%: session_id and sandbox_receipt are documented in-schema, but k, query, and delivery_receipt are undocumented anywhere. The description does not explain what k controls, what the free-text query accepts, or what delivery_receipt is for, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with pricing and a workflow sequence rather than a clear verb+resource statement; the actual action (running a prepaid query against an open session) is only inferable from the final step in the arrow chain and the tool name. The listing line names a concrete dataset (fdarecall FDA recall enforcement data) which helps, but the core purpose is buried. It does not differentiate from siblings like data_session_queries or data_preview.

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 explicit sequence (data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query) tells the agent the prerequisites before this tool can be called, which is real guidance. However, it gives no when-not-to-use condition, no mention of what to call instead if the session is unfunded, and no comparison with data_session_queries or data_preview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources