Skip to main content
Glama
Sign In
xippios-mcp

xippios-mcp

by xippios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

usda_psd_list_regions

Read-onlyIdempotent

Lists USDA PSD regions and their codes so you can map region_code values used by country listings, answered from packaged reference data without an upstream call.

Instructions

List PSD's regions with their codes, the values region_code of list_countries takes.

Answered from PSDData_GetRegions as packaged with this version (reference/regions.json), without an upstream call: 15 regions when packaged, in upstream order, from "R00" World and "R01" North America to "R18" East Asia. Upstream's list lacks "R15", the region of four countries in list_countries (Africa, NEC and three more); it is kept as upstream sends it. 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_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing provenance (PSDData_GetRegions / reference/regions.json), that no upstream call is made, the record count (15), upstream ordering, the notable gap at R15, and the meaning of meta.retrieved_at and meta.vintage. One tension: it says 'without an upstream call' while the openWorldHint=true annotation implies external-world interaction, so the annotation understates how closed the tool actually is, but this is not a safety contradiction.

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 key sentence is correctly front-loaded, but the trailing details about meta.retrieved_at and the empty meta.vintage add little decision value for an agent and stretch a simple enumeration tool across several sentences.

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?

With no output schema, the description carries the burden of describing returns, and it does so reasonably well: codes plus region names, ordering, count, and the meta provenance fields. Edge-case detail on the missing R15 region is covered.

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 nothing for the description to disambiguate; baseline 4 applies. It still helpfully clarifies that the returned region_code values are the input vocabulary for a sibling tool.

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?

The first sentence states a specific verb and resource ('List PSD's regions with their codes') and immediately ties the output to a named sibling parameter ('the values region_code of list_countries takes'). An agent can tell exactly what it gets and which tool consumes it without opening the schema.

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?

Usage is clearly implied: call this to resolve region codes before using list_countries' region_code filter. It gives no explicit when-not guidance or naming of alternatives, but for a zero-argument enumeration tool the intended call context is unambiguous.

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