Skip to main content
Glama

revoke_worker

Revoke one worker by label: its pass stops verifying at once and the label is never issued again. Needs your own pass. Configure Authorization: Bearer in your MCP client and omit the pass argument whenever headers are supported. The pass argument is a sensitive compatibility fallback for clients without header support. Arguments and credential-bearing results, including invoice, claim, free-tier claim and recovery results, may persist in client transcripts. Keep them private. A header takes precedence; conflicting credentials are refused.

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": {
      "label": "<label>"
    },
    "name": "revoke_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoConfigure Authorization: Bearer <pass> in your MCP client and omit the pass argument whenever headers are supported. The pass argument is a sensitive compatibility fallback for clients without header support. Arguments and credential-bearing results, including invoice, claim, free-tier claim and recovery results, may persist in client transcripts. Keep them private. A header takes precedence; conflicting credentials are refused.
labelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: immediate effect ('stops verifying at once'), permanence ('never issued again'), authentication requirement ('needs your own pass'), credential precedence, refusal of conflicting credentials, and transcript-persistence risk. This is unusually complete behavioral disclosure for an unannotated destructive tool.

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 first sentence is front-loaded and effective, but the credential paragraph is long and duplicates verbatim the schema description of 'pass', spending words on repetition rather than new information.

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 an irreversible mutation with no annotations and no output schema, the description covers effect, permanence, auth, and credential safety. It does not say what is returned on success or what error conditions besides conflicting credentials look like, which is a minor remaining gap.

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 50%: the 'pass' parameter is documented in the schema with text identical to the description, while 'label' has no schema description at all. The description only implies that 'label' identifies the single worker and that labels are never reissued, which is helpful but thin for the undocumented half of the 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 one worker') plus the exact scope ('by label') and the resulting effect ('its pass stops verifying at once and the label is never issued again'). That is enough to separate it from mint_worker and the invoice/claim family, though no sibling is named explicitly.

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?

It gives concrete operational guidance: you need your own pass, configure 'Authorization: Bearer <pass>' in the client, and omit the pass argument when headers are supported. It stops short of stating exclusions such as when revocation is inappropriate or what to do if the label is unknown.

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