List all API keys with their name, prefix, and last usage date. Identify which keys are active without exposing the full key value.
List API keys — Alle gültigen Schlüssel der Organisation mit Name, Präfix und letzter Nutzung. Der Schlüssel selbst ist nicht dabei, er wird nur bei der Erstellung gezeigt.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only/idempotent/non-destructive. The description adds a meaningful behavioral detail: the actual secret key is never returned, only shown during creation, which is beyond the annotation hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no redundant information; the limitation about the key not being included is valuable and placed upfront.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only list operation with no output schema, the description fully covers what is returned and the key limitation. Nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist and schema coverage is 100%, so the description need not explain parameters. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the specific operation ('List API keys') and describes exactly what is returned (organization's valid keys with name, prefix, last usage), distinguishing it from siblings like createApiKey and revokeApiKey.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clearly implies usage for listing keys and explicitly notes the key itself is not shown (only at creation), guiding when not to use this tool. Stops short of explicitly naming alternative tools, but context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.