Skip to main content
Glama

Get token info

get_token_info
Read-onlyIdempotent

Describe the token this connection uses: its name and client, scopes, the projects, environment kinds, environments and keys it can reach, when it expires, and the temporary access the user approved through request_access. Call it when another tool refuses for scope or reach, to see what this token can do before asking for more. With activity true it also lists what this token did, newest first (tool, project, keys touched and time, including before its last rotation, up to limit rows): use that to report your work or check whether an earlier call went through. It never shows other tokens or people, and on the Free plan activity reaches back 30 days. Access requests are in get_access_requests. Read-only, changes nothing. No scope needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoWith activity only: rows to return, 1 to 200. Default 50.
activityNoAlso list what this token did, newest first

Output Schema

NameRequiredDescriptionDefault
keysYesA list, or a sentence such as "every key" when nothing limits it
agentYes
tokenYesName of this token
clientYes
scopesYes
activityNo
projectsYesA list, or a sentence such as "every key" when nothing limits it
expiresAtYesISO 8601 timestamp, or a sentence when the token never expires
environmentsYesA list, or a sentence such as "every key" when nothing limits it
approvedAccessYes
environmentKindsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, and the description reinforces rather than contradicts them ('Read-only, changes nothing. No scope needed'). It adds genuinely new behavioral facts beyond the annotations: it never shows other tokens or people, Free-plan activity only reaches 30 days, and activity includes rows from before the token's last rotation.

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?

Front-loaded with what the token reveals, then when to call it, then the activity caveat. It is a single dense paragraph with a lot of clauses; slightly heavier than needed, but nearly every sentence adds a distinct fact.

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?

Despite an output schema existing, the description still names the returned fields and the ordering, covers the optional activity mode and its row cap, and states visibility limits and plan-based retention. Nothing an agent needs before calling a two-flag read tool is missing.

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 coverage is 100%, so baseline is 3, but the description goes further: it explains what 'activity' yields (tool, project, keys touched, time, newest first) and that 'limit' caps those rows, including pre-rotation history. That is meaning the schema's one-line param descriptions do not carry.

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?

Opens with a specific verb and resource plus an enumeration of exactly what is described: token name and client, scopes, reachable projects/environments/keys, expiry, and approved temporary access. An agent can distinguish it from get_access_requests purely from the text.

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?

Gives an explicit trigger ('call it when another tool refuses for scope or reach') and a purpose for that trigger ('see what this token can do before asking for more'). It also routes access-request data to the sibling get_access_requests, so the when-not case is covered.

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.

Resources