Skip to main content
Glama

Plan usage

get_usage
Read-only

Plan, locations used and allowed, requests and replies this month, and paid reads.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds the useful behavioral detail that the request/reply counts are scoped to 'this month' and that 'locations used and allowed' implies quota comparison, but says nothing about freshness, rate limits, or failure modes.

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?

A single economical sentence with the most important content (plan and location usage) front-loaded. It is a noun fragment without a verb, which is slightly awkward as an instruction but costs no space.

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?

With no parameters, no output schema, and full structured safety annotations, the description is the only place the return content can be communicated, and it does list the main buckets (plan, locations, monthly requests/replies, paid reads). It is adequate, though it omits return shape detail, such as whether values are counts, limits, or nested per-location breakdowns.

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 the baseline is 4. Since the request/reply figure is implicitly fixed to the current month and there are no arguments to disambiguate, there is no additional parameter meaning to convey.

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 enumerates the resource contents (plan, locations used/allowed, monthly requests and replies, paid reads), which tells an agent this is a plan/quota usage read rather than a stats or listing tool. It lacks a verb and never names the sibling it differs from (e.g. get_stats), so it falls short of 5.

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 guidance on when to call this versus get_stats, which plausibly overlaps on usage/metrics information. The agent must infer usage purely from the field list, with no stated conditions or exclusions.

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