Skip to main content
Glama

list_api_keys

List the caller's API keys (uuid, name, active flag, scopes, enabled checks). Use it to find a key's uuid before revoke_api_key, or to audit what exists; it never returns a key's secret, which create_api_key shows only once. Requires the api_keys:read scope.

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_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the security-relevant behavior that secrets are never returned, notes create_api_key shows a secret only once, and states the required api_keys:read scope. It stops short of describing ordering, pagination, or behavior for callers with zero keys, but the critical traits are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight clauses: what it returns, when to use it, and the security/permission constraint. The most decision-relevant information (what it returns, when to call it) is front-loaded with no filler.

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?

With no output schema and no parameters, the description must explain return contents itself, and it does so by listing the fields. Combined with the auth scope and the secret-handling caveat, an agent has everything needed to select and safely call it.

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?

The tool takes zero parameters, so the baseline applies; the description correctly adds nothing about inputs and instead spends its words on outputs. No parameter semantics are needed or missing.

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 the caller's API keys') and enumerates the returned fields (uuid, name, active flag, scopes, enabled checks). This cleanly separates it from sibling key tools like create_api_key and revoke_api_key.

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 conditions: find a key's uuid before calling revoke_api_key, or audit existing keys. It also implicitly rules out using this tool to obtain a secret and points to create_api_key for that, which is a genuine alternative routing.

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