Skip to main content
Glama

Replace my bearer token

rotate_token
Destructive

Replace your passport bearer token (for example after it leaked). The old token stops working at once; the new token is returned ONCE, so update your Authorization header right away. Needs a request signed with a passport key: a token (header or passport_token) is refused with signature_required, so a leaked token can never do this. A passport your MCP app signed in for has no bearer token and never gets one (app_sign_in_only): the app keeps the sign-in, out of your context. To end the passport instead: revoke_passport.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rotate_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses real consequences: the old token is invalidated immediately, the new token is shown ONCE and must be captured at once, and specific refusal codes with their reasons. It also explains a non-obvious asymmetry the annotations cannot convey — app-signed-in passports have no bearer token and never will — which prevents a futile call.

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?

Sentences are dense and front-loaded, leading with the action and its side effect before the auth requirements. It is on the long side for a single-parameter tool, and the app-sign-in explanation is somewhat elaborate, but nearly every clause carries decision-relevant information.

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?

For a one-optional-parameter destructive tool with no output schema, the definition covers everything an agent needs: the side effect, the one-time return of the new token (standing in for the absent output schema), the signing requirement, terminal failure modes, and the alternative tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the passport_token parameter is already documented as a fallback for when no header can be sent. The description reinforces the header-vs-body choice and confirms that a token cannot authorize this call, adding a little meaning beyond the schema but not much new syntax or format detail.

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 opens with a specific verb+resource ("Replace your passport bearer token") and immediately scopes it with the motivating case ("after it leaked"). It also distinguishes itself from revoke_passport, so the agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use it (post-leak rotation), the prerequisite condition (a request signed with a passport key), the cases where it is refused (token auth returns signature_required, app sign-in returns app_sign_in_only), and names the alternative for a different intent ("To end the passport instead: revoke_passport"). That is explicit when/when-not/alternative coverage.

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.