Skip to main content
Glama

AlgoRover Research

get_profile

Read-onlyIdempotent

读取当前已授权的 AlgoRover 账号资料。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameNo
emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's one added signal is '当前已授权的' – it operates on the caller's authenticated account context rather than an arbitrary account, which explains why it takes no parameters. Beyond that it says nothing about failure modes (e.g., missing or expired auth), so 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the action verb front-loaded and the scope qualifier attached to the resource. There is no filler, hedging, or restatement of the tool name, and nothing could be removed without losing meaning.

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?

With zero parameters, rich read-only annotations, and a declared output schema, the description carries only a small burden, and a short statement suffices. The one gap is that it never mentions a prerequisite such as a valid authorized session, which is relevant for a credential-scoped read.

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

Parameters4/5

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

The tool takes zero parameters, so there are no parameter semantics to document; the baseline for a parameterless tool is 4. The description's 'currently authorized' phrasing reinforces why no account identifier is needed, which is the only parameter-adjacent point worth making.

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 gives a specific verb and resource: 读取 (read) the currently authorized AlgoRover 账号资料 (account profile). That resource is unlike any sibling (backtests, strategies, research usage), so an agent can tell what this returns without opening the schema. It stops short of naming or contrasting an alternative, so it lands at 4 rather than 5.

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: an agent infers it should call this when it needs the signed-in account's profile. There is no explicit when-to-use statement, no exclusions, and no pointer to a sibling for other kinds of account or research data. The '当前已授权' scoping hints that no identifier is required, but that is inference rather than 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.