Skip to main content
Glama
Sign In

Magpie — USDA Ag Markets: Grain, Fertilizer, WASDE & Export Sales

by link.morningbrief
OverviewDiscussionsAdmin

get_wasde_history

Read-onlyIdempotent

Revision history of one WASDE projection figure (default ending_stocks) across monthly reports — how the estimate for a commodity and marketing year moved as successive WASDE reports landed. Use to study estimate revisions; use get_wasde_projection instead for the full current balance sheet. Read-only lookup of stored projections; no API key. Returns up to 24 monthly report values, oldest first, each with its report date and unit, for the requested commodity, attribute, and country (default WORLD).

Input Schema

NameRequiredDescriptionDefault
countryNoCountry code (WORLD, US, BR, AR). Default: WORLD aggregateWORLD
attributeNoProjection attribute (beginning_stocks, production, imports, exports, domestic_consumption, ending_stocks)ending_stocks
commodityYesCommodity slug (e.g. corn, wheat, soybeans)

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
provenanceYes
status_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "anyOf": [
+        {
+          "items": {
+            "properties": {
+              "captured_date": {
+                "type": "string"
+              },
+              "market_year": {
+                "type": "integer"
+              },
+              "release_date": {
+                "type": "string"
+              },
+              "report_date": {
+                "type": "string"
+              },
+              "unit": {
+                "type": "string"
+              },
+              "value": {
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "provenance": {
+      "properties": {
+        "as_of": {
+          "type": "string"
+        },
+        "cadence": {
+          "type": "string"
+        },
+        "cadence_detail": {
+          "type": "string"
+        },
+        "fetched_at": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        },
+        "source_detail": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "as_of",
+        "cadence",
+        "cadence_detail",
+        "fetched_at",
+        "source",
+        "source_detail"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "no_data",
+        "source_unavailable",
+        "withheld"
+      ],
+      "type": "string"
+    },
+    "status_detail": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "data",
+    "provenance"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / attribute / description
      Previous value: -"Projection attribute"New value: +"Projection attribute (beginning_stocks, production, imports, exports, domestic_consumption, ending_stocks)"
    • addedInput schema / properties / commodity / description
      Added value: +"Commodity slug (e.g. corn, wheat, soybeans)"
    • addedInput schema / properties / country / description
      Added value: +"Country code (WORLD, US, BR, AR). Default: WORLD aggregate"
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the safety profile needs no restating. The description does add real behavioral facts — no API key, up to 24 monthly values, oldest-first ordering, each point carrying its report date and unit. Solid supplementation without conflicting with the annotations.

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?

Three sentences, front-loaded with the core definition and the sibling routing before the mechanics. The trailing sentence mildly repeats the parameter list, but overall it is tight.

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?

Output schema exists so return values needn't be explained, and annotations cover safety; the description still supplies the cap of 24 points, ordering, per-point date/unit, and defaults. Nothing an agent needs in order to call this correctly is missing.

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% with enums and defaults documented, so the schema carries the parameter burden and baseline 3 applies. The description only restates the defaults (ending_stocks, WORLD) and maps parameters to the returned series, adding little beyond the schema.

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+resource: the revision history of a single WASDE projection figure across monthly reports, with the default attribute named up front. It explicitly distinguishes itself from get_wasde_projection, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the use case (studying estimate revisions) and the alternative (get_wasde_projection for the full current balance sheet), giving an explicit when-to-use / when-not-to-use split.

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

All Magpie — USDA Ag Markets: Grain, Fertilizer, WASDE & Export Sales 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