check-usageCheck your remaining credits, usage limits, and plan info
| Name | Required | Description | Default |
|---|---|---|---|
| verbose | No | Include detailed per-window rate limit breakdown |
| Name | Required | Description | Default |
|---|---|---|---|
| plan | Yes | Current plan tier | |
| status | Yes | Overall usage status | |
| credits | Yes | Remaining credit balance | |
| rateLimits | Yes | Rate limit status across all windows |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only and idempotent. The description adds valuable context about what data is returned (credits, limits, plan), going beyond the safety hints. No contradiction with annotations.
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 conveys the tool's purpose with zero wasted words. It is concise without sacrificing clarity.
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 the tool's simplicity (one optional parameter, output schema available, annotations covering safety), the description sufficiently covers purpose and scope. No additional details are necessary.
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%: the sole parameter 'verbose' is fully described in the schema ('Include detailed per-window rate limit breakdown'). The tool description does not need to repeat parameter details, so the baseline 3 is appropriate.
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 the specific verb 'check' and names concrete resources (remaining credits, usage limits, plan info). It is distinct from sibling tools like get-logs or list-models, which serve different purposes.
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 clearly implies when to use this tool: when you need to know your current credits, limits, or plan details. No explicit alternatives are needed because no sibling tool covers this functionality, and the context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tool set separates general consultation (consult-council) from specialized councils for tradeoffs, debugging, architecture, implementation planning, and code review. Session management and utility tools (logs, usage, models, sessions) are clearly distinct. Only minor potential overlap exists between consult-council and the specialized councils, but descriptions clarify the purpose of each.
All tools follow a consistent verb_noun pattern in snake_case (e.g., consult-council, get-session, list-models). Verbs are varied but predictable, and compound nouns are hyphenated consistently. No mixed conventions.
13 tools is appropriate for a platform that offers multiple council workflows plus session, log, and usage management. Each tool addresses a distinct need without unnecessary bloat.
The server covers the full lifecycle of a council-based workflow: model discovery (list-models), execution (consult-council and specialized councils), session retrieval (list-sessions, get-session), sharing (get-thread-link, set-thread-visibility), and operational support (check-usage, get-logs). Missing delete/update session tools are minor and not essential for the core purpose.