Skip to main content
Glama

Add token to profile

bind_token

Add an owner token to a BrewPage profile; needs an admin token of that profile.

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": {
      "token": "<token>"
    },
    "name": "bind_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesOwner token to add
ownerTokenNoAdmin token of the profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • 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"
  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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is covered. The description adds real value by disclosing the auth prerequisite (an admin token for that profile). It stops short of describing effects such as idempotency, replacement of an existing binding, or 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the action front-loaded and the prerequisite trailing after the semicolon. Nothing is wasted, though the prerequisite could be pushed further forward for scanability.

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 two-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description is nearly sufficient. The remaining gap is what 'bind' means behaviorally, e.g. whether it fails or overwrites when the token is already attached.

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% and both parameters already carry descriptions ('Owner token to add', 'Admin token of the profile'), so the description's mention of owner/admin tokens largely restates structured data. Baseline 3 applies since the schema does the heavy lifting and no format or validity details are added.

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 description states a specific verb and resource: adding an owner token to a BrewPage profile. It does not differentiate from the sibling mint_token, so an agent cannot tell from the text alone which of the two to use when a new token is needed versus binding an existing one.

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?

Usage is only implied: the description says an admin token of the profile is required, which hints at the prerequisite context. It never states when to prefer this over mint_token, nor what happens if the owner token is already bound to another profile, leaving the agent to infer the selection rule.

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.