Skip to main content
Glama

list_arena_strategies

Read-onlyIdempotent

Liste les stratégies d'une arène (BTC/ETH/SOL/BNB/…) classées par PnL, avec trades clôturés, position ouverte éventuelle et couverture. limit = nombre de lignes renvoyées (1 à 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
assetNoActif, ex. BTC, ETH, SOL, BNB.BTC
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds that results are PnL-ranked and include closed trades, an optional open position and coverage, but discloses no auth needs, rate limits or pagination behavior beyond the row 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?

Two front-loaded sentences with no filler: the first carries purpose, ordering and returned content, the second carries parameter semantics. Nothing is wasted, though the parameter note could be folded in slightly more tightly.

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?

An output schema exists, so return values need not be re-explained, and annotations carry the safety profile. The row cap, ordering and default asset behavior are covered, leaving only explicit sibling-routing guidance missing for a two-param list tool.

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

Parameters4/5

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

Schema coverage is only 50% – the limit parameter has no schema description at all – and the description compensates by defining it precisely as the number of returned rows bounded 1–40, matching the schema's min/max. The asset parameter is already documented in the schema, so the description adds little there.

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 ("Liste les stratégies d'une arène") plus the ordering key (classées par PnL) and returned content (trades clôturés, position ouverte, couverture). An agent can tell it apart from arena_snapshot or arena_leaderboard, though it never explicitly names which sibling to prefer over search_strategies.

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 only implied – wanting per-arena strategies sorted by PnL. There is no explicit when-to-use, when-not, or alternative named (e.g., search_strategies for filtered queries), and no mention of defaults or pagination context.

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