Skip to main content
Glama
Sign In

baton

by io.github.vinsenzo83
OverviewDiscussionsAdmin

baton_agent_record_result

독립 검증자의 서명 Receipt를 agent 실적으로 기록한다.

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": {
      "api_key": "<api_key>",
      "agent_id": "<agent_id>",
      "receipt": "<receipt>"
    },
    "name": "baton_agent_record_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYes
receiptYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It only says 'records a receipt' but does not disclose idempotency, side effects, authentication needs (beyond the api_key parameter), or whether it overwrites existing records.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it is in Korean, which may limit understanding for non-Korean agents. It lacks structured information like parameter lists or usage examples.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and no parameter details, the description is severely incomplete. It fails to explain what the tool returns, how to construct a valid receipt, or any behavioral constraints.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no information about the three parameters (api_key, agent_id, receipt). It does not explain what the receipt object expects or how agent_id is used.

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 records a signed receipt as agent performance (독립 검증자의 서명 Receipt를 agent 실적으로 기록한다). It specifies the verb (records) and resource (receipt as agent result). However, it does not differentiate from other recording tools like baton_cost_record or baton_git_record.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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