Skip to main content
Glama

Mint profile token

mint_token

Mint a profile token, shown once; needs an admin token of the profile.

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

Input Schema

NameRequiredDescriptionDefault
labelNo
scopeNoDefault publish
expiresInNoDefault: admin 90d, publish never
ownerTokenNoAdmin token of the profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / label / description
      Removed value: -"Optional label shown in the profile"
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"Admin token of the profile"
    • changedInput schema / properties / scope / description
      Previous value: -"publish (default) or admin (can manage tokens)"New value: +"Default publish"
  2. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Admin token of the profile. Default: BREWPAGE_OWNER_TOKEN."New value: +"Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations only say this is a non-read-only, non-destructive mutation. The description adds two behaviors the annotations do not: the token secret is displayed exactly once (so it cannot be retrieved later), and the call requires an admin token of the profile. It does not explain what happens to the token value on failure or whether minted tokens can be revoked.

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?

A single clause-dense sentence with no filler: the action, the one-time reveal, and the auth prerequisite are all front-loaded. Nothing could be removed without losing information.

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

Completeness3/5

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

For a mutation tool with annotation coverage and no output schema, the definition covers action, auth requirement, and one-time reveal adequately. It is thin on scope selection semantics (publish vs admin) and on label, and it does not resolve the tension that ownerToken is described as needed while the schema requires no parameters.

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 75% and both enum parameters already carry defaults in the schema, so the structured data does most of the work. The description reinforces ownerToken as the admin credential, but adds nothing about label, which is undocumented in both places. Baseline 3 fits this coverage level.

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?

States a specific verb and resource: 'Mint a profile token'. That is unambiguous about what the tool creates. It does not differentiate from the sibling bind_token, which an agent could plausibly confuse with token creation, leaving one gap.

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?

The description states the prerequisite ('needs an admin token of the profile'), which implicitly tells the agent when the call can succeed. It gives no explicit when/when-not guidance and does not name any alternative or say when to mint a publish-scoped token versus an admin-scoped one beyond the schema defaults.

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.