Skip to main content
Glama

List an app's service tokens

list_app_tokens
Read-onlyIdempotent

List a private app's service tokens: the bearer credentials scripts and other apps call it with. Each token shows its name, whether it is live, expired, or retiring (the old value of a rotation, which keeps working until the time shown), its expiry, who minted it and when, and the callers' env vars a rotation delivered it to. A token's value is never shown. Call it before rotate_app_token to find a token's name and the callers it will update. Requires connecting a Valet account. Requires the Admin role.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe app's name, as list_services shows it: the app whose tokens these are.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
appYesThe app the tokens belong to.
orgYesName of the Valet organization the call acted in.
tokensYesThe app's tokens, oldest first. Empty when it has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, closed-world read, and the description adds material context beyond them: token values are never returned, the three lifecycle states are defined (including that a retiring token keeps working until the shown time), and the auth/role requirements are surfaced. That is exactly the kind of behavior an agent needs to reason about sensitive credential data.

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 purpose, then behavior, then prerequisites, with no filler sentences. The middle sentence enumerating returned fields is long and partly duplicates what the output schema already provides, which is the only inefficiency.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, the description supplies everything else that matters: what is deliberately withheld (token value), how token states behave, the downstream workflow with rotate_app_token, and access requirements. Nothing needed to call it correctly 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 description coverage is 100%, so both parameters are already documented in the schema, including the "as list_services shows it" hint. The description adds no further meaning about the name format or when to supply org_name versus omitting it, so the baseline of 3 applies.

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?

States a specific verb and resource ("List a private app's service tokens") and immediately defines what a service token is ("the bearer credentials scripts and other apps call it with"), so the agent knows the object being enumerated. It also names the related sibling rotate_app_token, making the boundary between inspecting and rotating tokens explicit.

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 invocation condition: "Call it before rotate_app_token to find a token's name and the callers it will update," which tells the agent exactly why and when to reach for this tool rather than guessing. It also states two hard prerequisites (a connected Valet account and the Admin role), which are the main reasons a call would fail.

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