Skip to main content
Glama

BRAINIAC Product Safety & Recalls

Look up USDA FoodData nutrition

product-safety_usda-fooddata-nutrition
Read-onlyIdempotent

Return nutrient values per 100 g from USDA FoodData Central Foundation Foods and SR Legacy. Use when you need look up usda fooddata nutrition as a paid JSON result with no API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "product-safety_usda-fooddata-nutrition"
  }
}

Input Schema

NameRequiredDescriptionDefault
fdcIdNofdcId, integer, from any to 9007199254740991. Optional.
limitNolimit, integer, from 1 to 50. Required.
queryNoquery, string, length 2 to 100. Optional.
dataTypeNodataType, array. Optional.
nutrientsNonutrients, array. Optional.

Output Schema

NameRequiredDescriptionDefault
foodsNofoods. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context (results are per 100 g, output is JSON, no API key required, the call is billable/paid), but says nothing about pagination, the default limit of 10, maximum 50, or how an empty/no-match case is represented.

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?

It is short and front-loads the core purpose, which is good. However, the second sentence is grammatically broken ('when you need look up') and is largely tautological with the tool name, so it spends words without adding much signal.

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?

An output schema exists, so return shape needn't be explained, and the input schema is fully annotated. Still, for a five-parameter lookup tool with two distinct access modes (by fdcId versus by query/dataType/nutrients), the description does not clarify which parameters pair together, leaving an agent to infer usage from the schema alone.

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 all five parameters (fdcId, query, dataType, nutrients, limit) are already documented, and the baseline of 3 applies. The description only adds the per-100 g normalization and confirms the two source data types, which mirrors the enum rather than explaining parameter interaction (e.g., query vs fdcId lookup modes).

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 names a specific verb and resource ('Return nutrient values per 100 g from USDA FoodData Central Foundation Foods and SR Legacy') and scopes the value basis to per-100g, which is a meaningful detail. It is clearly a nutrition lookup rather than a recall search, so an agent can distinguish it from the listed siblings, though it does not explicitly name an alternative tool.

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?

The only usage cue is 'Use when you need look up usda fooddata nutrition', which restates the name rather than giving a condition for selecting this tool over anything else. The remaining clause ('paid JSON result with no API key') is auth/cost context, not when-to-use guidance or exclusions.

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