Skip to main content
Glama

Smarty-Pants AI

get_usage

Return this account's monthly usage and remaining plan allowance.

Args:
    year: Four-digit UTC year; defaults to the current year.
    month: UTC month from 1 to 12; defaults to the current month.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
monthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. It establishes that this is a retrieval operation scoped to 'this account' and to a month, which implies credentials determine the account, but it says nothing about permissions needed, rate limits, billing-period semantics, or whether historical months are retained. That is adequate but leaves real behavioral gaps for an unannotated tool.

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

Conciseness5/5

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

One front-loaded sentence states the outcome, followed by a compact args block with one line per parameter. Nothing is padded and no sentence is redundant with the purpose statement.

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

Completeness4/5

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

For a two-optional-parameter getter with an output schema covering the return values, the description supplies the essential call semantics (UTC units, defaults, account scoping). What is missing – retention of past months, auth requirements, rate limits – is secondary for a simple read 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?

Schema description coverage is 0% – the schema only shows nullable integers with null defaults. The description compensates well by stating that year is a four-digit UTC year and month is a UTC month from 1 to 12, and that both default to the current period, so the timezone and defaulting behavior are only knowable from the text.

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 uses a specific verb ('Return') and a specific resource ('this account's monthly usage and remaining plan allowance'), making the scope immediately legible. It does not name or differentiate from siblings, but the sibling names (scan_url, scan_urls) are unrelated to usage retrieval, so no confusion arises in practice.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no statement about when this tool should not be used or what an alternative would be. The only usage-adjacent information is the parameter defaults, which do not help the agent decide whether to call this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources