List API keys stored in ProphetKey and retrieve safe_key identifiers for use with the local proxy. Optionally filter by provider to narrow results.
List all API keys stored in ProphetKey. Returns safe_keys (not real keys) for use with the local proxy.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | No | Filter by provider name (optional) |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It discloses that the tool returns safe_keys and not real keys, which is a nontrivial behavior for agents to know. It does not mention additional traits like pagination or error behavior, but for a simple list operation this is adequate.
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 sentences with no filler. The core action is front-loaded, and the safe_keys caveat is a single clarifying clause.
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 simple optional-filter list tool, the description explains the return value (safe_keys) and its purpose (local proxy). No output schema exists, but the response concept is adequately conveyed for an agent to call and interpret the result.
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?
Schema coverage is 100%, so the provider parameter is already documented in the schema. The description adds no extra parameter semantics beyond the schema.
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 action (List all) and resource (API keys stored in ProphetKey), and clarifies that it returns safe_keys rather than real keys. This differentiates it from siblings like get_key_info, which targets a single key's details.
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?
The description implicitly signals this is the tool for enumerating available keys for the local proxy, but it does not explicitly state when to prefer it over siblings such as prophetkey_get_key_info or mention exclusions. No when-not-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.