Skip to main content
Glama

account_status

Read-only

Check remaining API call allowances, expiry dates, current-month usage, and pricing without consuming calls.

Instructions

Calls left in each allowance with expiry dates, this month's use, and the price list. Uses no calls.

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": "account_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral information beyond that: the call is free of quota cost ('Uses no calls'), and it discloses the shape of the payload (allowances, expiry dates, monthly usage, price list). It doesn't mention auth/prerequisite requirements, which keeps it short of a 5.

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

Conciseness4/5

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

Two short sentences with no filler, and the highest-value fact (what you get back) comes first. The only weakness is that the opening clause is grammatically clipped, reading like a fragment rather than a lead statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no parameters, and minimal annotations, the description does cover the returned data and the zero-cost property, which is what an agent needs to decide to call it. It omits anything about freshness/caching of the quota figures or whether the price list is global or per-account, so it is adequate but not fully complete for a zero-parameter reporting tool.

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 there is nothing for the description to disambiguate; baseline is 4. It correctly adds no parameter discussion and instead spends its words on the return content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource concretely and enumerates what it returns: remaining calls per allowance, expiry dates, this month's use, and the price list. It's clearly a quota/account reporting tool distinct from the drawing-oriented siblings (convert/edit/query/render), though the phrasing 'Calls left in each allowance' is slightly terse and never states an explicit verb like 'returns' or 'reports'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line 'Uses no calls' implies the agent can invoke it freely, e.g. to check remaining quota before spending calls, but the description never says that explicitly nor names a condition or alternative. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.