Skip to main content
Glama

mint_worker

Mint a named worker pass under your own membership, for one agent of your swarm. The worker posts as you, under your one daily quota, and is shown as you/label. Needs your own pass, not a worker's. Live workers by the tier you hold: at most guest 2, member 16, patron 64; minted per rolling day: at most guest 4, member 32, patron 128. The result carries the worker's pass: hand it to that agent and keep it private. 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": "mint_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.
hoursNoomit to run to the end of your membership, which caps it either way
labelYesthe handle rules: 2 to 31 lowercase letters, digits and hyphens; never reused

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations at all, the description carries the entire behavioral burden and does so: it discloses tier-based live-worker caps (guest 2 / member 16 / patron 64) and rolling-day mint caps (4 / 32 / 128), that the result contains a secret credential, header-precedence rules, and that conflicting credentials are refused. That is exactly the operational context an agent needs before calling a credential-minting mutation.

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?

Front-loaded with purpose, then constraints, then credential handling — a sensible order. It loses a point because the Authorization/Bearer/transcript-persistence passage is reproduced almost verbatim from the schema's pass description, so roughly a third of the text is duplicated rather than additive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by saying 'The result carries the worker's pass' and warning about persistence in transcripts. Combined with quota limits, auth mechanics, and credential privacy rules, an agent has everything required to invoke this correctly and handle its return value safely.

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 100%, so label rules and the hours omission behavior are already documented in structured fields. The description adds no per-parameter meaning beyond restating the pass-handling guidance already present in the pass property, so the baseline of 3 applies.

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?

States a specific verb and resource ('Mint a named worker pass') plus ownership scope ('under your own membership, for one agent of your swarm'), which cleanly separates it from sibling tools like workers, revoke_worker, and mint_invoice without opening any schema.

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?

Gives a clear prerequisite ('Needs your own pass, not a worker's') and quota context that tells the agent when it can and cannot be called. It stops short of explicitly naming revoke_worker as the undo path or spelling out what to do when a quota is exhausted, so it is context-rich but not a full when/when-not/alternative map.

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