Skip to main content
Glama

AlgoRover Research

get_research_usage

Read-onlyIdempotent

查询本人的运行中和排队任务数量。

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

Input Schema

NameRequiredDescriptionDefault
localeNoen

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so the safety profile is covered. The description adds one useful behavioral fact beyond them, that results are restricted to the caller's own tasks. However, it says nothing about whether the count is a snapshot, how 'queued' versus 'running' is defined, or what rate limits apply.

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 description is one front-loaded sentence with no filler or redundant restatement of the tool name. It is arguably too terse rather than too long; nothing needs to be cut.

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?

The tool is a simple read-only counter, it has an output schema, and the annotations are complete, so the description does not need to explain return values. What is missing is only the subject domain of the tasks being counted and a note that the description is in Chinese while its sibling tools are named in English.

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 parameter, locale, whose schema description coverage is 0% and whose enum values en/zh-CN are self-explanatory. The description does not mention the locale at all, so it neither explains why you would switch language nor compensates for the missing schema documentation. With only one trivially named parameter, this is a minor gap rather than a harmful one.

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?

Names a specific verb and resource: it queries the caller's own count of running and queued tasks, and it explicitly scopes the result to the current user (本人的). An agent can tell it is a count/status tool rather than a listing or mutation tool, though the description never says which domain the tasks belong to (research/backtest) and does not distinguish itself from siblings such as get_backtest or list_backtests.

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 when-to-use guidance and no named alternative. The agent has to infer that this is a status/quota check and that it should not use this tool to fetch actual task details or results, which siblings cover.

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.