Skip to main content
Glama

Verified market rates

market_rates
Read-onlyIdempotent

Median wholesale price per kg, litre or each, taken only from verified suppliers' own listings, and only where three or more verified suppliers list the product. Returns an empty list when no product has enough verified suppliers yet; then use search_prices.

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

Input Schema

NameRequiredDescriptionDefault
queryNoProduct words, e.g. 'salmon'. Empty for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the description's job is to add provenance and edge-case behavior, which it does: data comes only from verified suppliers' own listings, and results are suppressed below three suppliers. It does not say whether results are capped, paginated, or how stale the prices may be.

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 sentences, no filler, with the sourcing constraint and the suppression threshold front-loaded before the fallback instruction. Every clause carries information an agent needs.

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 annotations and no output schema, the description covers the important unknowns: unit basis (kg, litre, each), sourcing rules, and the empty-result condition. Only the shape of a populated result and any result-count limits go unaddressed.

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?

There is a single optional parameter with 100% schema coverage, so the schema already explains 'product words' and the empty-means-all default. The description adds nothing further about matching behavior, so the baseline of 3 applies.

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 definition names a precise computed resource — median wholesale price per unit — and pins down the population it is computed over: verified suppliers' own listings, with a three-supplier minimum. An agent can tell exactly what it will receive, and the empty-result clause separates it from the sibling search_prices.

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?

It gives an explicit fallback rule: when the verified-supplier threshold is not met the list is empty, and search_prices should be used instead. What it does not state is the forward case — when to prefer this over search_prices when data does exist, though the 'verified only' framing implies trust-quality use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources