Skip to main content
Glama

list_arena_strategies

Read-onlyIdempotent

Lists the strategies of one paper arena (BTC/ETH/SOL/BNB/…) ranked by PnL, with closed trades, any open position and coverage. limit = number of rows returned (1 to 40).

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

Input Schema

NameRequiredDescriptionDefault
assetNoAsset, e.g. BTC, ETH, SOL, BNB.BTC
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset / description
      Previous value: -"Actif, ex. BTC, ETH, SOL, BNB."New value: +"Asset, e.g. BTC, ETH, SOL, BNB."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context about ranking and included fields, but says nothing about pagination, whether strategies without closed trades appear, or what 'coverage' means. With annotations carrying the burden, a 3 is appropriate.

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 sentences, front-loaded with the resource and ranking, with no filler. The 'limit = number of rows returned (1 to 40)' clause is appended rather than integrated, but it earns its place by documenting an otherwise undescribed parameter.

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 an output schema covering return values and annotations covering safety, the description only needs to convey scope, ordering and row limits, which it does. The remaining gap is sibling disambiguation against list_native_strategies and arena_leaderboard, which would help an agent pick correctly.

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 50%: 'asset' is already documented in the schema with examples, while 'limit' has only minimum/maximum and no description there. The description partially compensates by defining limit as the number of rows returned and restating the 1–40 bound, but does not mention the default of 15 or the default asset BTC, both of which matter to callers.

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 ('Lists the strategies of one paper arena') plus the ordering ('ranked by PnL') and the returned content ('closed trades, any open position and coverage'), so the agent knows exactly what comes back. It does not explicitly contrast with siblings such as list_native_strategies or arena_leaderboard, though 'paper arena' implies the distinction.

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?

Usage is implied by the scope phrase 'one paper arena (BTC/ETH/SOL/BNB/…)', which tells the agent this is per-asset arena listing. There is no explicit when-to-use, when-not-to-use, or named alternative for cases like native strategies or leaderboard-level rankings, leaving selection to inference.

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