Skip to main content
Glama

writ_badge_revoke

Revoke one of the tenant's badge tokens.

Instructions

Revoke one of the tenant's badge tokens.

Its badge image URL 404s from that moment on, so embeds show a broken image rather than a stale claim. Only tokens belonging to the caller's tenant can be revoked.

Args: badge_token: The writ_badge_ token to revoke (shown once at mint time).

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": {
      "badge_token": "<badge_token>"
    },
    "name": "writ_badge_revoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
badge_tokenYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that the badge image URL 404s immediately and that cross-tenant revocation is blocked. It stops short of stating whether revocation is permanent or whether permissions beyond tenant ownership are required.

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 short, front-loaded with the action and consequence, and every sentence adds useful context. The Args section is concise and directly tied to the sole parameter.

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 one-parameter mutation tool with an output schema and no annotations, the definition covers the action, immediate effect, tenant scoping, and token origin. It could be more complete by clarifying reversibility or error behavior, but it is sufficient for correct invocation.

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?

Schema coverage is 0% for the single parameter, so the description must compensate. It explains that badge_token is the writ_badge_ token shown once at mint time, adding meaningful origin and format context beyond the bare string schema.

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 states a specific verb and resource: revoke a tenant badge token. It is clearly distinct from a generic revoke or mint tool by naming badge tokens and tenant scope, though it does not explicitly name sibling alternatives.

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?

It implies usage by describing the effect and the tenant restriction, including that only the caller's tenant tokens can be revoked. It does not explicitly say when to choose this over generic revoke tools or what to do with other token types.

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