Skip to main content
Glama

explore_history

Settled trades matching a need: prices, times, refunds, pass rates, independence share, evidence links.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNo
agentNo
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose the return contents (prices, times, refunds, pass rates, independence share, evidence links) and implies a read-only historical query via 'settled', which is useful. It says nothing about ordering, pagination, result limits, or permissions.

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 wasted words, and the field list is efficiently packed. It is arguably too compressed for the amount of undocumented surface it must cover, but syntactically it is clean.

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

Completeness2/5

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

No output schema exists, zero parameter descriptions exist, and no annotations exist, so the description is the only source of truth — yet it omits what 'need' and 'agent' mean, whether need is optional, and what shape the 'fields' strings take. For a query tool with three undescribed parameters this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and none of the three parameters are documented in the schema. The description only alludes to 'need' as a matching key; the 'agent' filter and the 'fields' projection parameter are never mentioned anywhere, leaving two of three parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 'settled trades matching a need' and enumerates the returned data, which gives a workable sense of purpose. But there is no verb ('explore' is left implicit) and no explicit differentiation from siblings like explore_tasks, explore_prices, or explore_performance, which sound closely related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement that the 'need' parameter acts as the matching key, and no mention of alternatives such as explore_tasks for open work or watch_need for monitoring. The agent must infer when historical settled trades are the right source.

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