Skip to main content
Glama

Get USDA Food

usda_get_food
Read-only

Get the full nutrient profile for one food by FDC ID. Returns all available nutrients (or a filtered subset via the nutrients[] param) with optional per-portion scaling. Use usda_search_foods to discover FDC IDs. Values are per 100 g (basisUnit "g"), except Branded foods FDC reports per 100 ml (basisUnit "ml") or per 100 of a label unit that fixes neither (basisUnit absent, basis unverified). Provide unit, optionally with quantity, to scale all nutrient values from that basis to that amount (e.g. quantity=200, unit="g" → per-200g values); a mass unit is applied to an ml or label-unit basis without conversion, and a notice says so. quantity defaults to 100 for g, oz, lb, and kg and to 1 for serving. Serving uses the valid portion FDC displays first (lowest sequenceNumber), or a positive finite Branded label size in g/GRM/GM (case-insensitive) when no portion exists; quantity multiplies that weight. A label in any other unit sets the basis rather than a serving weight, so it requires an explicit mass-unit request. quantity without unit is rejected. Narrow nutrients[] to specific IDs to reduce response size for focused queries. Set provenance=true to add to each nutrient how FDC obtained its value (derivation code, description, and source), its sample count (dataPoints), and the sample min, max, and median scaled with amount, each only where FDC sends it.

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": {
      "fdcId": "<fdcId>"
    },
    "name": "usda_get_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for quantity. "serving" uses the weight of the valid portion FDC displays first (lowest sequenceNumber), or a Branded label size in g/GRM/GM (case-insensitive) when no portion exists, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving.
fdcIdYesFDC ID of the food. Use usda_search_foods to discover IDs.
quantityNoAmount of food, in unit, to scale nutrient values to. Must be positive. Requires unit. Defaults to 100 when unit is g, oz, lb, or kg, and to 1 when unit is "serving". Omit both quantity and unit for the per-100 values FDC reports (per 100 g, or per 100 ml when basisUnit is "ml").
nutrientsNoFilter to specific nutrient IDs (e.g. [1003, 1004, 1005, 1008] for protein, fat, carbs, energy). Use usda_list_nutrients to look up IDs. Omit to return all available nutrients. Requested IDs the food does not report are listed in missingNutrients.
provenanceNoAdd to each nutrient what FDC records about its value: derivation (code, description, source), dataPoints (sample count), and min, max, median (sample spread, scaled with amount). Each is present only where FDC sends it: Survey (FNDDS) foods send none, Branded foods only a derivation. Off by default; it makes the response two to three times as large.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
fdcIdNoFDC ID of the food.
noticeNoBasis caveat when a food not reported per 100 g is scaled: the resolved amount was applied to its per-100 ml or unverified label-unit basis without conversion.
gtinUpcNoGTIN/UPC barcode as FDC stores it, leading zeros kept (e.g. "011110044174"). Branded items only.
dataTypeNoFDC data source: SR Legacy, Foundation, Survey (FNDDS), or Branded.
scaledToNoScaling basis when unit was provided. Absent when returning per-100 values.
basisUnitNoWhat the per-100 nutrient values are measured in: "g" for every non-Branded food and for Branded labels in g/GRM/GM, "ml" for Branded labels in ml/MLT. Absent when the label unit (e.g. IU, MG) fixes neither, so the basis is unverified.
brandNameNoBrand name. Branded items only.
nutrientsNoNutrient values for this food, per 100 of basisUnit or scaled to the scaledTo basis.
brandOwnerNoBrand owner. Branded items only.
allPortionsNoAll named portions for this food, in FDC's display order: ascending sequenceNumber, ties as FDC lists them, unnumbered portions last.
descriptionNoFull USDA food name (e.g. "Chicken, broilers or fryers, breast, meat only, raw").
ingredientsNoIngredient list from label. Branded items only.
servingInfoNoThe portion one serving weighs: the first of allPortions (the one FDC displays first), or, when the food has no portion, a Branded gram-label serving identified in its description.
servingSizeNoServing size from the product label, in servingSizeUnit. Branded items only.
foodCategoryNoUSDA food category (e.g. "Poultry Products"): the food category for SR Legacy and Foundation, the label category for Branded, the WWEIA category for Survey (FNDDS). Absent when FDC reports none.
publicationDateNoDate this food entry was published in FDC, as YYYY-MM-DD (e.g. "2019-04-01"). A date FDC sends in another form is returned as sent.
servingSizeUnitNoUnit for servingSize as FDC reports it (e.g. "GRM", "MLT", "IU"); it sets basisUnit. Branded items only.
missingNutrientsNoRequested nutrient IDs this food's profile does not report, deduplicated, in request order. Absent when nutrients[] was omitted or every requested ID is present.
householdServingFullTextNoServing as the label words it (e.g. "1 cup"). Branded items only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / provenance
      Added value: +{
      +  "default": false,
      +  "description": "Add to each nutrient what FDC records about its value: derivation (code, description, source), dataPoints (sample count), and min, max, median (sample spread, scaled with amount). Each is present only where FDC sends it: Survey (FNDDS) foods send none, Branded foods only a derivation. Off by default; it makes the response two to three times as large.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / nutrients / items / properties / dataPoints
      Added value: +{
      +  "description": "Number of samples behind the value, as FDC sends it; with provenance=true only. SR Legacy sends it on every value (0 for calculated and assumed values), Foundation on analytical values; Branded and Survey (FNDDS) send none. A count, never scaled.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / nutrients / items / properties / derivation
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "How FDC obtained the value; with provenance=true only. Foundation and Branded send one on every value, SR Legacy on some (a measured SR Legacy value can carry only dataPoints), Survey (FNDDS) on none. Absent when FDC sends none, never inferred. Code \"Z\" is an assumed zero, not a measurement.",
      +  "properties": {
      +    "code": {
      +      "description": "FDC derivation code (e.g. \"A\", \"NC\", \"Z\", \"LCCS\").",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "What the code means, as FDC words it (e.g. \"Analytical\", \"Calculated\", \"Summed\").",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Source category FDC files the derivation under (e.g. \"Analytical or derived from analytical\", \"Calculated or imputed\", \"Assumed zero\"). Absent when FDC sends none.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "description"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / nutrients / items / properties / max
      Added value: +{
      +  "description": "Highest sample value, in the same unit and basis as amount and scaled with it; with provenance=true only. Foundation sends it on most values, SR Legacy on some; Branded and Survey (FNDDS) send none.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / nutrients / items / properties / median
      Added value: +{
      +  "description": "Median sample value, in the same unit and basis as amount and scaled with it; with provenance=true only. Foundation sends it on most values; SR Legacy, Branded, and Survey (FNDDS) send none.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / nutrients / items / properties / min
      Added value: +{
      +  "description": "Lowest sample value, in the same unit and basis as amount and scaled with it; with provenance=true only. Foundation sends it on most values, SR Legacy on some; Branded and Survey (FNDDS) send none.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / publicationDate / description
      Previous value: -"Date this food entry was published in FDC."New value: +"Date this food entry was published in FDC, as YYYY-MM-DD (e.g. \"2019-04-01\"). A date FDC sends in another form is returned as sent."
  2. Changed5 schema fields changed
    • changedInput schema / properties / unit / description
      Previous value: -"Unit for quantity. \"serving\" uses the first valid portion weight, or a Branded label size in g/GRM/GM (case-insensitive) when no portion exists, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving."New value: +"Unit for quantity. \"serving\" uses the weight of the valid portion FDC displays first (lowest sequenceNumber), or a Branded label size in g/GRM/GM (case-insensitive) when no portion exists, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving."
    • changedOutput schema / properties / allPortions / description
      Previous value: -"All named portions for this food, in FDC order."New value: +"All named portions for this food, in FDC's display order: ascending sequenceNumber, ties as FDC lists them, unnumbered portions last."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: The FDC ID does not exist in the database. `quantity_without_unit`: quantity is provided but unit is omitted. `no_portion_data`: unit=\"serving\" was requested but the food has no valid portion or supported Branded gram-label serving. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: The FDC ID does not exist in the database. `quantity_without_unit`: quantity is provided but unit is omitted. `no_portion_data`: unit=\"serving\" was requested but the food has no valid portion or supported Branded gram-label serving. `retry_deadline_exceeded`: FDC did not answer within the call's 45-second budget, across every attempt. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "not_found",
      -  "quantity_without_unit",
      -  "no_portion_data"
      -]New value: +[
      +  "not_found",
      +  "quantity_without_unit",
      +  "no_portion_data",
      +  "retry_deadline_exceeded"
      +]
    • changedOutput schema / properties / servingInfo / description
      Previous value: -"First available portion definition, or a Branded gram-label serving identified in its description."New value: +"The portion one serving weighs: the first of allPortions (the one FDC displays first), or, when the food has no portion, a Branded gram-label serving identified in its description."
  3. Changed19 schema fields changed
    • changedInput schema / properties / nutrients / description
      Previous value: -"Filter to specific nutrient IDs (e.g. [1003, 1004, 1005, 1008] for protein, fat, carbs, energy). Use usda_list_nutrients to look up IDs. Omit to return all available nutrients."New value: +"Filter to specific nutrient IDs (e.g. [1003, 1004, 1005, 1008] for protein, fat, carbs, energy). Use usda_list_nutrients to look up IDs. Omit to return all available nutrients. Requested IDs the food does not report are listed in missingNutrients."
    • changedInput schema / properties / quantity / description
      Previous value: -"Amount of food, in unit, to scale nutrient values to. Must be positive. Requires unit. Defaults to 100 when unit is g, oz, lb, or kg, and to 1 when unit is \"serving\". Omit both quantity and unit for per-100g values (FDC database native basis)."New value: +"Amount of food, in unit, to scale nutrient values to. Must be positive. Requires unit. Defaults to 100 when unit is g, oz, lb, or kg, and to 1 when unit is \"serving\". Omit both quantity and unit for the per-100 values FDC reports (per 100 g, or per 100 ml when basisUnit is \"ml\")."
    • changedOutput schema / properties / allPortions / description
      Previous value: -"All named portions for this food."New value: +"All named portions for this food, in FDC order."
    • addedOutput schema / properties / allPortions / items / properties / amount
      Added value: +{
      +  "description": "How many of the described unit gramWeight covers (0.5 for \"0.5 cup\"), when FDC sends one. Absent for Survey (FNDDS) portions, whose description carries the amount.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / allPortions / items / properties / description / description
      Previous value: -"Portion description."New value: +"Portion description (e.g. \"0.5 cup\", \"1 small/regular\")."
    • addedOutput schema / properties / basisUnit
      Added value: +{
      +  "description": "What the per-100 nutrient values are measured in: \"g\" for every non-Branded food and for Branded labels in g/GRM/GM, \"ml\" for Branded labels in ml/MLT. Absent when the label unit (e.g. IU, MG) fixes neither, so the basis is unverified.",
      +  "enum": [
      +    "g",
      +    "ml"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / foodCategory / description
      Previous value: -"USDA food category (e.g. \"Poultry Products\"). Absent for some branded items."New value: +"USDA food category (e.g. \"Poultry Products\"): the food category for SR Legacy and Foundation, the label category for Branded, the WWEIA category for Survey (FNDDS). Absent when FDC reports none."
    • addedOutput schema / properties / gtinUpc
      Added value: +{
      +  "description": "GTIN/UPC barcode as FDC stores it, leading zeros kept (e.g. \"011110044174\"). Branded items only.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / householdServingFullText
      Added value: +{
      +  "description": "Serving as the label words it (e.g. \"1 cup\"). Branded items only.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / missingNutrients
      Added value: +{
      +  "description": "Requested nutrient IDs this food's profile does not report, deduplicated, in request order. Absent when nutrients[] was omitted or every requested ID is present.",
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Basis caveat when a food not reported per 100 g is scaled: the resolved amount was applied to its per-100 ml or unverified label-unit basis without conversion.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / nutrients / description
      Previous value: -"Nutrient values for this food, per 100g or scaled to the scaledTo basis."New value: +"Nutrient values for this food, per 100 of basisUnit or scaled to the scaledTo basis."
    • changedOutput schema / properties / nutrients / items / properties / amount / description
      Previous value: -"Nutrient amount — per 100g, or per scaledTo.gramWeight when unit is provided."New value: +"Nutrient amount — per 100 of basisUnit, or per scaledTo.gramWeight when unit is provided."
    • changedOutput schema / properties / scaledTo / description
      Previous value: -"Scaling basis when unit was provided. Absent when returning per-100g values."New value: +"Scaling basis when unit was provided. Absent when returning per-100 values."
    • changedOutput schema / properties / scaledTo / properties / gramWeight / description
      Previous value: -"Gram weight resolved from quantity and unit (for serving, quantity × servingInfo.gramWeight) — all nutrient values are per this many grams."New value: +"Amount resolved from quantity and unit (for serving, quantity × servingInfo.gramWeight); all nutrient values are per this many grams. With basisUnit \"ml\" it is applied as millilitres, and with no basisUnit as label units, without conversion."
    • addedOutput schema / properties / servingInfo / properties / amount
      Added value: +{
      +  "description": "How many of the described unit gramWeight covers (0.5 for \"0.5 cup\"), when FDC sends one. Absent for Survey (FNDDS) portions, whose description carries the amount, and for a label serving.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / servingInfo / properties / description / description
      Previous value: -"Portion description, or label-serving provenance with source size, unit and available household text."New value: +"Portion description: the Survey (FNDDS) portion text, or the amount, measure unit, and modifier (e.g. \"0.5 cup\"); for a Branded gram label, \"Label serving:\" with its size, unit, and household text."
    • addedOutput schema / properties / servingSize
      Added value: +{
      +  "description": "Serving size from the product label, in servingSizeUnit. Branded items only.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / servingSizeUnit
      Added value: +{
      +  "description": "Unit for servingSize as FDC reports it (e.g. \"GRM\", \"MLT\", \"IU\"); it sets basisUnit. Branded items only.",
      +  "type": "string"
      +}
  4. Changed5 schema fields changed
    • changedInput schema / properties / unit / description
      Previous value: -"Unit for quantity. \"serving\" is the food's first defined portion weight, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving."New value: +"Unit for quantity. \"serving\" uses the first valid portion weight, or a Branded label size in g/GRM/GM (case-insensitive) when no portion exists, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: The FDC ID does not exist in the database. `quantity_without_unit`: quantity is provided but unit is omitted. `no_portion_data`: unit=\"serving\" was requested but the food has no portion data. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: The FDC ID does not exist in the database. `quantity_without_unit`: quantity is provided but unit is omitted. `no_portion_data`: unit=\"serving\" was requested but the food has no valid portion or supported Branded gram-label serving. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / scaledTo / properties / gramWeight / description
      Previous value: -"Gram weight resolved from quantity and unit (for serving, quantity × the first portion weight) — all nutrient values are per this many grams."New value: +"Gram weight resolved from quantity and unit (for serving, quantity × servingInfo.gramWeight) — all nutrient values are per this many grams."
    • changedOutput schema / properties / servingInfo / description
      Previous value: -"First available portion definition, if present."New value: +"First available portion definition, or a Branded gram-label serving identified in its description."
    • changedOutput schema / properties / servingInfo / properties / description / description
      Previous value: -"Portion description (e.g. \"1 cup\", \"4 oz\")."New value: +"Portion description, or label-serving provenance with source size, unit and available household text."
  5. Changed7 schema fields changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Amount of food to scale nutrient values to. Must be positive. When provided, unit is required. Omit for per-100g values (FDC database native basis)."New value: +"Amount of food, in unit, to scale nutrient values to. Must be positive. Requires unit. Defaults to 100 when unit is g, oz, lb, or kg, and to 1 when unit is \"serving\". Omit both quantity and unit for per-100g values (FDC database native basis)."
    • changedInput schema / properties / unit / description
      Previous value: -"Unit for quantity. \"serving\" uses the food's first defined portion weight. Required when quantity is provided."New value: +"Unit for quantity. \"serving\" is the food's first defined portion weight, multiplied by quantity. Required when quantity is provided. Given alone, scales to 100 g, oz, lb, or kg, or to 1 serving."
    • changedOutput schema / properties / nutrients / description
      Previous value: -"Nutrient values for this food, per 100g or scaled to the requested quantity."New value: +"Nutrient values for this food, per 100g or scaled to the scaledTo basis."
    • changedOutput schema / properties / nutrients / items / properties / amount / description
      Previous value: -"Nutrient amount — per 100g, or scaled to quantity+unit if provided."New value: +"Nutrient amount — per 100g, or per scaledTo.gramWeight when unit is provided."
    • changedOutput schema / properties / scaledTo / description
      Previous value: -"Scaling basis when quantity+unit were provided. Absent when returning per-100g values."New value: +"Scaling basis when unit was provided. Absent when returning per-100g values."
    • changedOutput schema / properties / scaledTo / properties / gramWeight / description
      Previous value: -"Gram weight resolved from quantity+unit — all nutrient values are per this many grams."New value: +"Gram weight resolved from quantity and unit (for serving, quantity × the first portion weight) — all nutrient values are per this many grams."
    • changedOutput schema / properties / scaledTo / properties / quantity / description
      Previous value: -"Numeric quantity provided in the request."New value: +"Quantity applied — the requested value, or the default for unit (100 for g, oz, lb, kg; 1 for serving)."
  6. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "fdcId",
      +      "description",
      +      "dataType",
      +      "nutrients"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: The FDC ID does not exist in the database. `quantity_without_unit`: quantity is provided but unit is omitted. `no_portion_data`: unit=\"serving\" was requested but the food has no portion data. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "not_found",
      +            "quantity_without_unit",
      +            "no_portion_data"
      +          ],
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "fdcId",
      -  "description",
      -  "dataType",
      -  "nutrients"
      -]
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld, but the description goes far beyond: it explains the reporting basis (per 100 g, per 100 ml for Branded, or an unverified label unit), how unit+quantity rescale everything, that a mass unit is applied to an ml/label basis without conversion plus a notice, default quantity per unit, that quantity without unit is rejected, and that provenance inflates the response 2-3x. That is exactly the kind of behavior an agent cannot infer from structured fields.

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 purpose is correctly front-loaded, but the body is one dense block that repeats the schema's unit/quantity semantics nearly verbatim, and the portion-fallback and label-unit rules are hard to parse in prose. The content is valuable; the packaging is heavier than necessary.

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

Completeness5/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 values need not be explained, and the description still covers every edge that could cause a wrong call: default scaling, missing unit, no-conversion basis changes, unavailable nutrient IDs, and provenance cost. Nothing an agent needs for a correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds real meaning, notably the missingNutrients behavior, the no-conversion rule for mass units on an ml/label basis, and the portion-selection rule (lowest sequenceNumber first, then Branded label size in g/GRM/GM). Some of it restates the schema's own unit/quantity text, which limits it to a 4 rather than 5.

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?

States a specific verb and resource up front ('Get the full nutrient profile for one food by FDC ID'), and makes scope explicit: one food, keyed by FDC ID, with all nutrients by default or a filtered subset via nutrients[]. The reference to usda_search_foods for ID discovery further separates it from the search/list siblings.

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?

Gives clear routing guidance ('Use usda_search_foods to discover FDC IDs') and two usage-driven tips: narrow nutrients[] for focused queries, set provenance=true only when you need derivation/sample data. It does not state when to prefer usda_get_foods or usda_compare_foods over this one, so the plural/batch alternative is left implicit.

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.