Skip to main content
Glama

recent_trades

Retrieve recent anonymized public trades on KrystalineX to check market activity; no user identity is included.

Instructions

Get the most recent anonymized public trades on KrystalineX. Useful for "is the market active?" questions. Trades carry no user identity.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of trades to return (1–100, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

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 carries the full load. It usefully discloses the privacy trait ('anonymized', 'no user identity'), but says nothing about ordering (presumably newest-first), data freshness/latency, or whether the call is read-only.

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?

Three short sentences, front-loaded with the core action and scope. Minor redundancy: 'anonymized' and 'Trades carry no user identity' express the same privacy fact twice.

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?

For a simple single-parameter read tool this is close to adequate, but with no output schema the agent cannot learn the shape of a trade record (price, side, timestamp), and the description does not compensate.

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 'limit' parameter is fully documented in the schema (1–100, default 20). The description adds no meaning about the parameter, so the 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: 'Get the most recent anonymized public trades on KrystalineX'. The 'is the market active?' framing helps separate it from aggregate siblings like total_volume, though no sibling is named 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?

Offers one concrete use case ('is the market active?' questions) which implies when to reach for it, but gives no guidance on when not to use it or which alternative to pick for aggregated or historical views.

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