Skip to main content
Glama

AlgoRover Research

search_strategies

Read-onlyIdempotent

打开 AlgoRover Research 内嵌策略目录,搜索公开策略并返回精确版本。含连字符的完整策略 slug 精确匹配,普通关键词按相关性搜索。首次目录显式传入会话语言 locale:中文用 zh-CN,英文用 en;用户指定语言时优先采用。后续详情和目录保持相同语言。

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

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
limitNo
queryNo
cursorNo
localeNoen
filtersNo

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, yet the description still adds real behavior: hyphenated full slugs trigger exact match while ordinary keywords are relevance-ranked, results are pinned to exact versions, and locale must stay consistent across subsequent calls. It does not mention pagination via cursor or the 25-item cap, which is the main remaining gap.

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?

The purpose and matching modes are front-loaded, then locale rules follow as actionable instructions. Sentences are dense but each carries information; the only mild weakness is that the locale-persistence rule is packed into the same block as the matching semantics.

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 exists, so return-value shape needn't be described, and the annotations cover the safety profile. However, for a six-parameter search tool with a cursor, sort enum, and nested filters object, the absence of any pagination or sorting guidance leaves the definition short of complete.

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% across six parameters, so the description carries the full burden. It meaningfully explains query (slug vs keyword matching) and locale (zh-CN vs en, user preference wins), but says nothing about sort, limit, cursor, or filters, leaving four parameters undocumented anywhere. That partial compensation is real but insufficient for a zero-coverage schema.

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 opens with a specific verb and resource: it opens the embedded strategy catalog, searches public strategies, and returns exact versions. It further distinguishes two retrieval modes (exact slug match with hyphens vs relevance-ranked keyword search), which lets an agent distinguish it from get_strategy or prepare_strategy. It never names a sibling, so sibling differentiation is implied rather than stated.

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?

Guidance is limited to locale usage: pass the session language on the first catalog call, prefer a user-specified language, and keep later detail/catalog calls in the same language. There is no explicit statement of when to search here versus calling get_strategy directly, nor any exclusion or prerequisite beyond locale. Usage context is implied by the search semantics.

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.