Skip to main content
Glama

Usda Fdc

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Food

get_food
Read-onlyIdempotent

Full food record by FDC id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fdc_idYesFDC id (e.g. 1102704)
formatNoabridged | full (default full)
nutrientsNoComma-sep nutrient numbers to restrict response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fdcIdNoFDC food identifier
dataTypeNoType of food data
descriptionNoFood description
foodNutrientsNoArray of nutrient data for food
publishedDateNoDate food was published

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "fdc_id": 1102704
+  },
+  {
+    "fdc_id": 1102704,
+    "format": "abridged",
+    "nutrients": "208,205,291"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Full food record from USDA FDC",
+  "properties": {
+    "dataType": {
+      "description": "Type of food data",
+      "type": "string"
+    },
+    "description": {
+      "description": "Food description",
+      "type": "string"
+    },
+    "fdcId": {
+      "description": "FDC food identifier",
+      "type": "number"
+    },
+    "foodNutrients": {
+      "description": "Array of nutrient data for food",
+      "items": {
+        "properties": {
+          "amount": {
+            "description": "Nutrient amount",
+            "type": "number"
+          },
+          "nutrient": {
+            "properties": {
+              "name": {
+                "description": "Nutrient name",
+                "type": "string"
+              },
+              "number": {
+                "description": "Nutrient identifier number",
+                "type": "string"
+              },
+              "unitName": {
+                "description": "Unit of measurement",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "publishedDate": {
+      "description": "Date food was published",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds limited value. It mentions 'full food record', implying a complete response, but does not elaborate on return format or pagination.

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 a single sentence without wasted words. However, it is almost too brief; a bit more context could improve clarity without losing conciseness.

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?

Given the presence of an output schema and comprehensive annotations, the description provides enough context. It indicates the tool retrieves a single food record by ID, which is sufficient for a straightforward read operation.

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 coverage is 100%, so the description does not need to add parameter details. The description mentions 'FDC id' which aligns with the required parameter, but adds no new meaning beyond the schema.

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 states the action (get) and resource (full food record by FDC id). It is succinct and unambiguous, but does not distinguish from sibling tools like 'list_foods' or 'search_foods', which also deal with food data.

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 provided on when to use this tool versus alternatives such as 'search_foods' or 'nutrients_for_food'. The description lacks context about prerequisites or preferred scenarios.

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

All Usda Fdc 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