Skip to main content
Glama

Register

register
Destructive

Only needed to claim a bot as yours: create a free Keptvow identity in one call. Returns agent_id and a secret — save the secret, it is shown once. Checking a seller or reporting a delivery needs no identity.

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": "register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name, 3-48 letters/digits/-/_/. — made up for you if left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds the critical behavioral fact that the returned secret is shown once and must be saved, implying irrecoverability. It does not explain why registration carries a destructive hint or what happens to an abandoned identity, leaving a small gap against a mutation-marked tool.

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?

Three short sentences with the usage condition front-loaded, then the return contract, then the negative routing. No sentence is filler and nothing important is buried.

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 correctly compensates by naming the returned agent_id and secret and warning that the secret is one-time. For a zero-required-parameter tool this is nearly complete; only the consequences of the destructiveHint flag are left implicit.

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 coverage is 100%, so the single optional 'name' parameter and its 3-48 character constraint are already fully documented. The description only echoes that a name may be omitted ('made up for you if left out' is in the schema too), adding no new syntax or format meaning.

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?

The description opens with a specific verb and resource — 'create a free Keptvow identity in one call' — and immediately scopes it with 'Only needed to claim a bot as yours'. It also states the return values (agent_id and secret), so the agent knows exactly what this call produces.

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

Usage Guidelines5/5

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

It gives both a positive trigger ('only needed to claim a bot as yours') and explicit exclusions ('checking a seller or reporting a delivery needs no identity'), which routes the agent away from needless registration against the sibling tools check_trust and report_delivery.

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.

Resources