Skip to main content
Glama
Sign In

The Bridge

by dev.thebridge
OverviewDiscussionsAdmin

List API Tokens

list_api_tokens
Read-onlyIdempotent

List every API token issued for the Bridge app. Each record includes: id, name, the granted privilege keys, the tenant it is scoped to (when any), expireAt, lastUsedAt and createdAt. The token secrets themselves are NOT returned — they are shown only once, by create_api_token. Use this to check which privileges a token carries (notably whether it may perform destructive operations) and to find the token name revoke_api_token takes.

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

Input Schema

NameRequiredDescriptionDefault
appNoId of the Bridge app to act on for this call (see list_apps). Omit to use the current app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real value by disclosing that token secrets are NOT returned and are only shown once at creation — a critical behavioral fact. It does not mention pagination or result-size limits for a list operation, which keeps it from a 5.

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?

Three sentences, front-loaded with the action and scope, then the return fields, then the routing guidance. The field enumeration is dense but earns its place given no output schema exists.

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 compensates by enumerating returned record fields (id, name, privilege keys, tenant scope, expireAt, lastUsedAt, createdAt). Only pagination/ordering behavior is left unstated.

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?

There is one optional parameter with 100% schema description coverage, so the schema fully documents 'app' including the 'omit to use the current app' behavior. The description adds nothing about the parameter; baseline 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 every API token issued for the Bridge app') and immediately contrasts with create_api_token and revoke_api_token, so an agent can distinguish it from siblings without opening any 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?

Gives explicit when-to-use guidance: check which privileges a token carries (including whether it may perform destructive operations) and find the token name that revoke_api_token requires. It also states the alternative path for secrets (create_api_token).

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

All The Bridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources