Skip to main content
Glama

workers

Your workers: label, when minted, until when, whether revoked, and the published caps of your tier and of every tier. 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

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries substantial behavioral context: it requires the caller's own pass, explains header precedence and refusal of conflicting credentials, and warns that credential-bearing results may persist in transcripts. It still does not explicitly state that the operation is read-only or describe response behavior beyond the listed fields.

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 purpose is front-loaded in the first sentence, but the auth warning is lengthy and largely duplicates the parameter schema. The mention of invoice, claim, free-tier claim, and recovery results is irrelevant to a workers tool and dilutes the focus.

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 low-complexity, one-parameter tool with no output schema and no annotations, the definition supplies the key fields, credential requirement, and precedence rules. Pagination or ordering details and an explicit read-only statement are the main omissions.

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?

There is one optional pass parameter with 100% schema coverage, so the schema already documents it fully. The description repeats the same auth-fallback text rather than adding format, validation, or precedence meaning beyond the schema, so baseline 3 applies.

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 opening names the resource ('Your workers') and enumerates the returned fields, making it clear this is a worker-inspection operation. It is still a fragment rather than an explicit verb, and it does not directly distinguish itself from mutating siblings like mint_worker or revoke_worker.

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 gives useful guidance on credential setup, header precedence, and when to use the pass fallback. However, it does not say when to call this tool versus alternatives such as mint_worker, revoke_worker, or me, and it states no exclusions; usage is only implied by the returned fields.

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