Retrieve API key usage details—tier, credits used and remaining, monthly clearances, and billing period—to monitor spending and approval limits.
Get usage for this API key: tier, credits_used, credits_remaining, clearances_this_month, period_start, and period_end.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and no parameters, the description carries the disclosure burden. It makes clear this is a read operation on the caller's key and enumerates returned fields, but it omits auth requirements, rate limits, or whether the period is configurable.
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?
A single front-loaded sentence that states the operation and immediately enumerates the returned fields. No sentence is wasted.
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 zero-parameter read tool with no output schema, the description supplies the return fields an agent needs. Minor gaps like error behavior or period semantics are acceptable at this complexity.
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?
The tool takes zero parameters, so the baseline is 4. The description appropriately does not invent parameters and instead explains what the implicit API-key context yields.
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?
The description uses a specific verb and resource ('Get usage for this API key') and names the exact fields returned. It is clearly distinguishable from sibling tools like clearances_get and keys_create, which cover different resources.
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?
Usage is implied by 'for this API key', suggesting the tool reports the calling key's own usage. However, it doesn't say when to prefer it over siblings, nor mention any prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.