get_account_statusCheck your current plan, available tools, and credit balance to resolve tier errors and see what actions are permitted.
See your current plan, available tools, and credit balance. Call this if a tool returns a tier error or you want to know what tools are available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.20.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare read-only, open-world, idempotent, and non-destructive. The description adds that it reveals plan, tools, and credits, but does not elaborate on whether the information is cached, real-time, or subject to rate limits. With annotations covering safety, the added context is modest.
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, front-loaded with what it does, then the when-to-use condition. No wasted words.
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?
Given no parameters, annotations covering safety, and no output schema, the description adequately tells the agent what it returns and when to call it. It could mention that this is a lightweight diagnostic tool, but it is largely complete.
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, so baseline is 4. The description correctly implies no input is needed, matching the empty 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?
The description clearly states it returns the current plan, available tools, and credit balance; a specific verb+resource. This is distinct from siblings like get_auth_matrix or list_modules.
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?
Explicitly states when to use it: 'Call this if a tool returns a tier error or you want to know what tools are available.' This provides a clear trigger condition, though no explicit alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.