Skip to main content
Glama

Unregister current agent

unregister_self

Remove the current agent registration for your session and immediately release the MCP session to an unregistered state without deleting other agents.

Instructions

Remove the caller session's current agent registration. This tool only unregisters the currently bound agent identity; it does not delete other agents. On success it deletes the agent row and immediately releases the current MCP session back to an unregistered state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the concrete side effects: the agent row is deleted and the MCP session is immediately returned to an unregistered state. That is a solid disclosure of a destructive, immediately effective operation, though it omits whether the registration is recoverable, any permission requirements, or the error behavior for an already-unregistered caller.

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, front-loaded with the action and scope before the success behavior. Every sentence adds a distinct fact — action, scope limit, side effect — with no repetition of the title.

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?

For a zero-parameter tool with no output schema and no annotations, the definition covers what the agent needs: what is removed, what is not removed, and what state the session ends in. It is only slightly incomplete in not addressing failure or repeat-invocation behavior.

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 is no parameter meaning to convey and the baseline of 4 applies. The description correctly avoids inventing options such as an agent-id override, which reinforces that only the caller can be unregistered.

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 states a specific verb and resource ("Remove the caller session's current agent registration") and immediately bounds the scope ("does not delete other agents"), which is exactly the distinction an agent needs to keep this apart from sibling tools like register_agent or list_agents.

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?

The exclusion clause ("only unregisters the currently bound agent identity; it does not delete other agents") gives a clear when-not condition, and the caller-session framing implies when it applies. It stops short of naming an explicit alternative tool or stating preconditions such as what happens if the session is already unregistered.

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