Skip to main content
Glama

Usage

usage

Device-minutes used this month, per day and per device.

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": "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?

With no annotations, the description carries the full burden, and it does disclose two real behavioral facts: the window is fixed to 'this month' and the data is broken down per day and per device. It does not state that the operation is read-only, whether results are account-scoped or require auth, or how large the response is (up to 31 days x N devices).

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?

A single front-loaded sentence with zero filler; the two most decision-relevant facts (metric and granularity) come first.

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?

The tool is trivial to invoke, but with no annotations and no output schema, the description is the only source of truth about the returned shape and it stops at 'per day and per device' — no field names, units, or totals. Adequate to invoke, thin for interpreting results.

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 per the baseline this scores 4. The description usefully explains why no parameters are needed by pinning the range to the current month, though it does not say whether any filtering (device, date) is possible at all.

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 (device-minutes used this month) and its aggregation granularity (per day, per device), which is specific enough to distinguish it from the device_* lifecycle siblings and from task/profiles reporting tools. It falls short of 5 only because the verb is implied ('used') rather than stated as an action such as 'report' or 'retrieve'.

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 alternatives such as task_status, task_artifacts, or device_list, nor any stated prerequisite or context. The agent must infer from the name alone that this is the billing/quota reporting 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