SiteCheck Company Records

USDA FoodData Central food search: FDC ID, description

gov_usda_fooddata_central

Read-only

USDA FoodData Central food search: FDC ID, description, data type (Branded, Foundation, SR Legacy and others), brand owner and publication date, for a food name. Search results only; nutrient values are not returned here. Usually answers in about 9 s, up to 17 s on slower calls; allow a 30 s timeout. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "query": "<query>"
    },
    "name": "gov_usda_fooddata_central"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Foods to return, 1 to 10 (default 5)
`query`	Yes	Food name, 2 to 60 characters

Output Schema

Name	Required	Description	Default
`foods`	No
`query`	No
`source`	No
`checkedAt`	No
`totalHits`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior3/5

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

The description discloses exactly the operational behavior the annotations cannot: typical ~9 s latency, worst case ~17 s, a recommended 30 s timeout, and $0.002 USDC per successful call via x402 with failures not charged. That is meaningful cost and timeout context an agent needs before invoking, and it is consistent with readOnlyHint=true and openWorldHint=true. It does not clarify whether a single call is billed per invocation regardless of result count or how the limit parameter affects cost.

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

Conciseness5/5

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

Purpose and returned fields are front-loaded in the first clause, the scope exclusion follows immediately, and latency and pricing are compressed into a single trailing sentence. No sentence is redundant with the title or schema.

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?

With an output schema present, return values need not be re-explained, and the latency and pricing disclosures cover the main remaining uncertainty for a paid, open-world search. Only minor gaps remain around cost behavior with respect to the limit parameter and result ranking/pagination.

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 parameters are already fully documented (query is 2–60 chars, limit is 1–10 with default 5). The description only restates that the search is 'for a food name', adding no syntax, format, or edge-case guidance beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

Names a specific verb and resource (USDA FoodData Central food search) and enumerates the exact fields returned (FDC ID, description, data type, brand owner, publication date), which lets an agent distinguish it from any nutrient-lookup or generic open-data tool without opening the schema.

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?

Explicitly bounds the scope with 'Search results only; nutrient values are not returned here', which tells the agent when this tool is the wrong choice. It stops short of naming the alternative to use for nutrient values, so routing is implied rather than prescribed.

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

All SiteCheck Company Records tools Inspect

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

Need Help?