Skip to main content
Glama
Sign In

baton

by io.github.vinsenzo83
OverviewDiscussionsAdmin

baton_upgrade

Pro/Team 업그레이드 인보이스를 생성한다. USDT/USDC를 Tron(TRC-20) 또는 BSC(BEP-20) 지갑으로 송금하는 안내를 반환. api_key가 유료 계정이 된다.

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": {
      "plan": "<plan>",
      "api_key": "<api_key>"
    },
    "name": "baton_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
api_keyYes이 키가 유료 계정이 됨(강력·비공개 문자열)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description mentions that the api_key becomes a paid account, indicating a state change. However, with no annotations, it does not disclose whether the operation is idempotent, reversible, or if it requires authentication beyond the api_key. Some transparency is provided, but gaps remain.

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?

The description is three sentences with no superfluous content. The main action is first, followed by payment details and the effect on the api_key. Highly efficient.

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 no output schema, the description adequately explains what the tool returns (payment instructions). For a simple two-parameter tool, it covers the essential behavior, though it could mention expected response format or error conditions.

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?

Schema description coverage is 50% (only api_key has a description). The tool description adds context about USDT/USDC and wallet networks, but does not elaborate on the 'plan' parameter beyond its enum values. It partially compensates for the schema gap.

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 clearly states that the tool generates an upgrade invoice for Pro/Team plans and returns payment instructions for USDT/USDC. It is specific about the resource (invoice) and action (generate), but does not explicitly differentiate from sibling tools like baton_verify_plan, which might cause minor confusion.

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?

No guidance on when to use this tool versus alternatives (e.g., baton_verify_plan, baton_account). There is no mention of prerequisites or scenarios where this tool should or should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All baton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources