Skip to main content
Glama

AlgoRover Research

delete_research_data

DestructiveIdempotent

仅在用户明确要求时永久删除个人研究数据并撤销当前授权。删除期间暂停访问;完成后可使用同一账号重新登录授权,开始新的研究,旧数据不会恢复。

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": {
      "confirmation": "<confirmation>"
    },
    "name": "delete_research_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoen
confirmationYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
schema_versionNo2.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare destructiveHint=true and idempotentHint=true. The description adds that access is suspended during deletion, that the account can re-authorize and start fresh afterwards, and that old data is unrecoverable — the operational consequences an agent needs before firing an irreversible call.

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?

Three tight clauses with the safety precondition front-loaded ahead of the deletion mechanics and the recovery path. No redundant restatement of the title or annotations.

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?

An output schema exists, so return values need not be described, and the annotations carry the safety profile. The description covers the lifecycle consequences of the deletion well; only the required confirmation parameter is left unexplained, which is a modest gap for a two-parameter tool.

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% for both parameters. The description never mentions the required 'confirmation' token or the 'locale' enum, so an agent must infer the confirmation requirement purely from the schema's const value. With zero coverage, the description should have compensated and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource combination — permanently delete personal research data and revoke the current authorization. Scope is clear enough to separate it from the sibling 'delete_backtest_result', which handles a single artifact rather than the whole account's research data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit precondition: only when the user explicitly requests it. That is a real when-to-use gate rather than an implied one. It stops short of naming alternatives (e.g. deleting a single backtest vs. all data), so it does not reach a 5.

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.