Skip to main content
Glama

Read quota usage

get_usage
Read-onlyIdempotent

Read current billing-period usage for conversations and messages per channel against plan limits, plus AI token consumption.

Instructions

Read the store's usage for the current billing period: conversations and messages per channel against the plan's limits, and AI tokens.

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

Output Schema

NameRequiredDescriptionDefault
channelsYes
ai_tokensYes
period_endYes
period_startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no repeating. The description adds meaningful substance beyond that: exactly which usage dimensions are returned and that quantities are expressed against the plan's limits, which tells the agent the response is comparative rather than raw counters. It omits freshness/latency and whether the period is fixed, keeping it below 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.

Conciseness5/5

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

A single sentence that front-loads the scope ('current billing period') and then lists the returned dimensions. Every clause carries distinct information; no filler, no restatement of the title.

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 zero-argument read with a full annotation set and an existing output schema, the description covers purpose, scope, and content adequately. A note on how current the figures are, or confirmation that limits come from the active plan only, would close the remaining gap.

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 no parameters, so there is no parameter meaning to add; the baseline for a zero-parameter tool applies. Nothing in the description misleads about inputs, and the absence of options is consistent with the empty schema.

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

Purpose5/5

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

A specific verb ('Read') plus a specific resource ('the store's usage') scoped to 'the current billing period', then enumerated into concrete dimensions (conversations, messages per channel, plan limits, AI tokens). This is unmistakably a quota/usage report and cannot be confused with the content-oriented siblings like get_conversation or search_knowledge.

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 scope 'for the current billing period' implies when this is the right call (checking consumption against plan limits), but there is no explicit when-to-use/when-not statement and no named alternative. The guidance is inferable rather than stated.

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