Skip to main content
Glama

Latest trades across platforms

get_recent_trades
Read-only

The most recent executed fills across all four platforms (or one), newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20.
platformNoLimit to one platform. Omit for all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platform / description
      Added value: +"Limit to one platform. Omit for all four."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing sort order ('newest first') and that only executed fills are returned, but it says nothing about the default/explicit limit interaction or result size beyond the schema's cap.

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 tightly written sentence with the resource and ordering front-loaded and no filler. It is arguably terse to the point of missing routing context, but nothing in it is wasted.

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 two-parameter read tool with full annotation coverage the essentials are present, but with no output schema the description never indicates what a 'fill' contains or how results are shaped. A brief note on the returned trade fields would close the remaining gap.

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 100%, so both parameters are fully documented in the schema, including the default of 20 and the 'omit for all four' behavior. The description only echoes the platform scoping ('or one') and adds no format or semantics beyond the schema -- baseline 3.

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+resource ('most recent executed fills') plus scope ('across all four platforms (or one)') and ordering ('newest first'). It implicitly separates itself from get_property_trades by being platform-scoped rather than property-scoped, but never names that sibling, so differentiation is inferential rather than explicit.

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 and no mention of alternatives such as get_property_trades or get_platform_overview. The only routing hint is the platform parameter's 'Omit for all four', which lives in the schema rather than the description.

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