Skip to main content
Glama

Strategies

get_strategies
Read-only

The user's own strategies: id, name, market, and which one is active in each market. A signal's strategy_id is one of these ids.

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

Input Schema

NameRequiredDescriptionDefault
marketNohk = Hong Kong, us = United States, cn = China A-shares.

Output Schema

NameRequiredDescriptionDefault
errorNo
limitNo
totalNo
offsetNo
warningsNo
strategiesNo
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / error / properties / reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

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, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds meaningful scope information beyond that - that only the authenticated user's own strategies are returned - plus the cross-reference to signal.strategy_id. It does not say what happens with the market filter or how multiple markets are ordered, so it stops short of rich behavioral detail.

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 short sentences, front-loaded with what the tool returns, with no filler. The second sentence earns its place by linking the output to signal.strategy_id, though the phrasing is slightly clipped.

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 format need not be explained, and the single parameter is fully documented in the schema. What remains mildly incomplete is the behavior of the optional market filter and the relationship to the singular get_strategy sibling, neither of which is addressed.

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?

There is a single optional market parameter with 100% schema description coverage and a documented enum (hk/us/cn), so the schema already carries the semantics. The description adds nothing about the parameter, notably not whether omitting it returns all markets; with full schema coverage this is the 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?

The description names the resource (the user's own strategies) and enumerates the fields returned (id, name, market, active-per-market), so the agent knows this is a list of strategy records. It is implicitly distinguished from the singular get_strategy by 'strategies' and 'which one is active in each market', but that contrast is never stated outright.

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: the sentence 'A signal's strategy_id is one of these ids' tells the agent this tool resolves strategy ids seen in signals, which is genuinely useful routing context. However, there is no explicit when-to-use versus get_strategy, and nothing about whether to call this before get_strategy for a single record.

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.