Skip to main content
Glama

AlgoRover Research

get_strategy

Read-onlyIdempotent

读取公司已发布策略及其现有解析状态、预设和市场。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
localeNoen
versionNo

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is fully covered. The description adds that the response includes parsing status, presets, and markets, which is useful scope information, but it says nothing about what 'published' entails, whether unpublished/versioned strategies are reachable, or what happens with openWorld access.

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 front-loaded clause with no filler or repetition. It is efficient, though its brevity is partly under-specification rather than disciplined economy.

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?

An output schema and rich annotations reduce the burden, and the description correctly frames the tool as a read of a published strategy. However, with three undocumented parameters and an unexplained null-default version selector, an agent still lacks enough to invoke it confidently in non-trivial cases.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and does not: slug, locale (en/zh-CN), and version are never mentioned. In particular, the meaning of version=null (does it mean latest published?) and the effect of locale are left entirely to inference.

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 uses a clear verb (读取/read) with a specific resource (公司已发布策略/company's published strategy) and adds the payload scope (parsing status, presets, markets). It does not name a sibling such as search_strategies to distinguish lookup-by-slug from search, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the natural alternative (search_strategies) for finding a strategy when the slug is unknown. The only implicit cue is 'published', which hints that drafts cannot be fetched here.

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.