crop-prices

get_group_snapshot

Fetch current prices for every crop in a selected group in one call to build market overviews or brief sections without querying each commodity individually.

Instructions

Current price for every crop in a group in one call. Use for overviews like "how are grains doing?" or as the data for a market brief section.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group": "<group>"
    },
    "name": "get_group_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`group`	Yes	Which crop group to price.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/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 behavioral burden; it does establish that results are current (not historical) and cover a whole group in a single call. It says nothing about freshness/latency, permissions, or whether crops missing quotes are omitted, which matters for a pricing snapshot.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the capability and followed by the use case. No filler, no redundancy with the title or schema.

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?

For a one-parameter read tool with full schema coverage and no annotations, the description covers what it does, when to reach for it, and roughly what comes back ('current price for every crop'). The absence of any note on return shape details or quote freshness is a minor gap given there is no output schema.

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?

The single 'group' parameter is fully described in the schema with an enum of all seven groups, so coverage is effectively 100% and the baseline applies. The description adds no further meaning about group selection, so it neither helps nor hurts.

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 resource (current price for every crop in a group) and adds the batch qualifier 'in one call', which implicitly contrasts with per-commodity pricing siblings like get_current_price. It stops short of naming a sibling explicitly, so differentiation is inferential rather than stated.

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?

Gives concrete use cases ('how are grains doing?', 'data for a market brief section') that map cleanly onto the overview-vs-single-price split. It offers no explicit when-not-to-use or named alternative, so the routing decision still requires the agent to recognize that this is the bulk variant.

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

Deploy Server