Skip to main content
Glama

mint_scoped_token

Mint a restricted child token from a multi-use credential for offline delegation to sub-agents. Attenuates scope, uses, and spend caps without additional payment.

Instructions

Mint a scoped, capped child credential from a multi-use credential you already hold for an endpoint, to hand to a sub-agent. Attenuates OFFLINE (no payment, no round-trip): the child is a normal L402 token the worker spends with call_api or a plain client, and the gateway enforces every cap. Attenuation is tighten-only — a child can never widen scope or exceed the parent's remaining uses/sats. Give at least one restriction. Requires a held multi-use credential for this endpoint (a single-use payment has nothing to delegate). Revoke the whole tree with revoke_token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe endpoint path the held bundle is for (e.g. '/v1/history/candles')
slugYesThe API slug the credential is for (e.g. 'btc-intel')
expiryNoChild expiry as an ISO 8601 timestamp (e.g. '2026-08-01T00:00:00Z') or Unix milliseconds; must be no later than the parent's expiry
n_usesNoCap the child to this many requests (must not exceed the parent's remaining n_uses)
path_prefixNoRestrict the child to request paths at or under this prefix (must be at or under the parent's path scope)
spend_cap_satsNoCap the child's cumulative spend in sats (must not exceed the parent's max_sats)
Behavior4/5

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

With no annotations, the description covers key behaviors: offline attenuation, tighten-only, child token type, gateway enforcement, and prerequisite of a multi-use credential. Lack of output format is acceptable given no output schema.

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?

Three sentences, front-loaded with the main action, followed by offline nature and constraints. No wasted words.

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?

Given 6 parameters, no annotations, and no output schema, the description adequately covers prerequisites, behavioral constraints, and relationship to revoke_token. Minor missing details like return value are acceptable.

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 covers all 6 parameters with descriptions. The description adds general guidance ('Give at least one restriction') but does not elaborate on individual parameters beyond the schema.

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?

The description clearly states the tool mints a scoped, capped child credential from a multi-use credential for delegation to a sub-agent. It distinguishes from siblings like revoke_token by explicitly mentioning it.

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?

The description explains when to use (when holding a multi-use credential and needing to delegate) and mentions the offline nature. It references revoke_token for revocation but does not explicitly list alternatives or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signaltech-org/bolthub-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server