Skip to main content
Glama

explore_prices

Per capability and per skill: what settled trades paid (min/p25/median/p75/max), hours to settlement, pass rates, providers, open prices. Inputs for your own bid or ask; the market quotes no fair price.

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

Input Schema

NameRequiredDescriptionDefault
skillNo
capabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does more than most: it discloses the aggregate statistics returned, that the data is restricted to settled trades, and that the market provides no fair price — an important expectation-setting behavior. It stops short of stating read-only semantics or whether results are paginated or cached.

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?

Two compact sentences, front-loaded with the returned metrics and closed with the usage caveat. The telegraphic metric list is dense but every item earns its place; only the phrasing is slightly clipped.

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 and no annotations, the description has to convey both content and shape, and it enumerates the statistics and dimensions well enough for an agent to decide to call it. Missing only edge-case behavior for optional params and result scope/size.

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 coverage is 0%, so the description must compensate. "Per capability and per skill" does explain that the two parameters are aggregation/grouping dimensions rather than free-text filters, which adds real meaning. It does not say what happens if both are supplied, if neither is supplied, or whether matching is exact.

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 description names the resource (settled trade prices and market statistics) and the breakdown dimensions (per capability, per skill), and enumerates the metrics returned (min/p25/median/p75/max, hours to settlement, pass rates, providers, open prices). That distinguishes it from siblings like evaluate_market and capability_priors, though it never states the action explicitly ("explore" is only in the name).

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?

"Inputs for your own bid or ask" implies the tool is used before quoting, and "the market quotes no fair price" warns not to expect a single authoritative number. But there is no explicit when-to-use versus explore_performance, evaluate_market, or capability_priors, and no mention of what happens with no filters.

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