Skip to main content
Glama
Sign In
xippios-mcp

xippios-mcp

by xippios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

usda_psd_list_units_of_measure

Read-onlyIdempotent

List USDA PSD units of measure with their IDs and descriptions so you can interpret unit_id values in PSD data records.

Instructions

List PSD's units of measure with their ids, the unit_id of every data record.

Answered from PSDData_GetUnitsOfMeasure as packaged with this version (reference/unitsOfMeasure.json), without an upstream call: 42 units when packaged, in upstream order, e.g. 8 (1000 MT), 4 (1000 HA), 26 (MT/HA). Descriptions are upstream's, padded with spaces to 20 characters ("(1000 MT) "). enums.UnitId names the same ids. meta.retrieved_at is when the package fetched the list (2026-10-28, UTC); meta.vintage is empty, as upstream gives the list no release identifier.

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": "usda_psd_list_units_of_measure"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavior beyond them: the result is served from packaged data "without an upstream call," contains 42 units in upstream order, and carries padding-to-20-characters quirk plus the meta.retrieved_at / meta.vintage fields. These are exactly the details an agent needs to interpret results correctly.

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?

It is front-loaded with the purpose and id relationship in the first sentence, then layers detail in descending importance. Every note earns its place except arguably the ``meta.vintage`` note, which is minor trivia, and the total length is justified for a zero-parameter tool whose payload is undocumented elsewhere.

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?

With no input parameters and no output schema, the description must carry the entire burden of describing the response, and it does: record shape (id plus description), count, ordering, example ids, the space-padding quirk, the enums alias, and meta fields. Nothing needed to call or interpret this tool 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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless schema applies. The description uses the space instead to characterize the return payload, which is the more useful investment here.

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 opening sentence gives a specific verb and resource: "List PSD's units of measure with their ids," and adds the key framing detail that the id is "the unit_id of every data record." That is unambiguous about what the tool returns, but it never explicitly contrasts itself with the sibling list tools (commodities, countries, regions), so it falls just short of the 5 bar.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: mentioning "the unit_id of every data record" hints the list is for decoding unit ids, and "``enums.UnitId`` names the same ids" flags an alternative lookup path. However, there is no explicit "call this before get_data to resolve unit codes" instruction and no when-not guidance.

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

Deploy Server

Other Tools