crop-prices

list_commodities

List crops with available price sources and optionally filter by commodity group to find supported commodities and their data origins.

Instructions

List the crops this server has prices for, with their available sources.

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

Input Schema

Name	Required	Description	Default
`group`	No	Only show crops in this group.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry the burden. 'List' implies a safe read-only, non-destructive operation and the phrase 'with their available sources' hints at the response shape, but nothing states whether results are complete, cached, or ordered. For a simple enumeration tool this is adequate but thin.

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?

A single front-loaded sentence with no filler. It could carry one more clause (e.g., that results can be filtered by group) at little cost, but nothing is wasted.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has one optional parameter, and an output schema exists so return values need not be described. Still, the description omits the existence of the group filter and does not frame this as the discovery entry point for the sibling price tools.

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 description coverage is 100% and the single optional 'group' parameter with its enum is fully documented in the schema. The description adds no information about the filter, so baseline 3 applies.

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?

States a specific verb and resource ('List the crops') plus a scope qualifier ('this server has prices for') and notes the payload includes available sources. This distinguishes it from price-fetching siblings such as get_current_price and get_price_history, though it never names them explicitly.

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 only implied: as an enumeration tool it is the natural first step before calling get_current_price or get_price_history. There is no explicit statement of when to use this versus compare_commodities or get_group_snapshot, and no mention of the filter-driven alternative.

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

Deploy Server