brewpage-mcp

Mint profile token

mint_token

Generate a new BrewPage profile token using an admin token, choose publish or admin scope and 30d/90d/1y/never expiry; the token is shown once.

Instructions

Mint a new profile token with an admin token; the new token is shown once. Scope publish (default) or admin; expiry 30d, 90d, 1y or never.

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

Name	Required	Description
`label`	No	Optional label shown in the profile
`scope`	No	publish (default) or admin (can manage tokens)
`expiresIn`	No	Default: admin 90d, publish never
`ownerToken`	No	Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.3Oct 30, 2026

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)."

Changed2 schema fields changedv1.15.0Oct 27, 2026

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
```

Addedv1.13.0Oct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the crucial behavior that the token is displayed only once and is unrecoverable afterward, plus the authority required to mint it. It stops short of describing what happens to a previously minted token's validity or rate/auth failure modes.

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 tight sentence pair; the operation and its one-time-visible result are front-loaded, then the parameter choices. No filler.

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?

With no output schema, the description correctly covers the essential return fact that the token value is revealed once. The remaining defaults (ownerToken from env) are already in the schema, so nothing an agent needs to invoke it is missing.

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 the schema already documents all four parameters including defaults. The description restates the scope and expiry vocabularies without adding semantics such as what an admin token can subsequently do or how label is surfaced.

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?

Specific verb+resource ('Mint a new profile token') with a key effect stated ('the new token is shown once'). It does not differentiate itself from the closest sibling bind_token, so an agent must infer the distinction between minting and binding a token.

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 states a prerequisite ('with an admin token') and enumerates the allowed scope/expiry choices, which gives usable context. However, it never says when to mint versus when to bind a token via bind_token, and gives no exclusions or failure conditions.

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