Skip to main content
Glama

AlgoRover Research

get_strategy_download

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": {
      "strategy_ref": "<strategy_ref>"
    },
    "name": "get_strategy_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
strategy_refYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already grant readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real value beyond them by clarifying that this returns metadata only and neither installs nor executes the artifact — a meaningful boundary given the sibling set contains prepare/start operations. It omits whether the version must match exactly or how the sha256 is verified.

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 zero filler, and the negative constraint is placed immediately after the purpose. It is arguably too terse for a tool whose parameters are fully undocumented, but no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema means return values need not be described, and annotations cover safety. However, a tool taking a 3-field nested reference plus a sha256 pattern and a locale enum gets only one sentence, leaving an agent unable to determine how to construct a valid request or what makes the strategy reference valid.

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 the burden and it largely does not. '确定版本' hints that the reference is version-pinned and '公开策略' hints at the slug scope, but the nested StrategyRef fields (slug, version, package_sha256), their patterns, and the locale enum are left entirely unexplained.

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: obtain download information for a public strategy at a pinned version. The distinction from a file-delivery or execution tool is made explicit ('不安装或执行文件'), though it does not name a sibling such as get_strategy or prepare_strategy as the alternative.

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 by the noun phrase 'download information' plus the negative clause 'does not install or execute the file', which signals the boundary of what this call is for. There is no explicit statement of when to choose this over get_strategy or get_backtest_report_download, and no prerequisite or exclusion guidance.

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.