Skip to main content
Glama

Sign out of Todrawn

todrawn_logout
DestructiveIdempotent

Revoke this agent’s Todrawn access token and remove it from the local machine, ending authenticated access. Use it to log out or secure access when the token is no longer needed.

Instructions

Revokes this agent's access token and deletes it from this machine. The person can also revoke it on their Todrawn profile page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and openWorld=true, so the safety profile is covered. The description adds concrete value by specifying exactly what is destroyed (the access token) and where (deleted from this machine), plus the fact that server-side revocation is also possible via the profile page. It stops short of saying what the agent should do afterward.

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?

Two short sentences, front-loaded with the primary effect and followed by the secondary revocation path. Nothing is redundant, though the second sentence is more user-facing context than agent guidance.

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 no-parameter, no-output-schema tool, the definition covers the essential effect and its scope. The one meaningful omission is post-conditions: whether the agent's subsequent tool calls will fail and what re-auth path exists.

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?

Zero parameters, so there is no schema semantics to supplement; baseline is 4. The description does not waste words inventing parameter detail, which is appropriate.

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?

States a specific verb pair and resource: 'Revokes this agent's access token and deletes it from this machine.' An agent immediately knows this is the end-of-session operation. It does not explicitly name todrawn_login as its counterpart, but the intent is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the operation (sign out) rather than stated. It notes the person can also revoke on their profile page, which is a useful parallel path, but there is no explicit 'call this when...' condition, no warning about subsequent calls failing, and no guidance on re-authentication.

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