Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get the organization's usage across all numbers

get_usage
Read-onlyIdempotent

Get WhatsApp message and contact usage for the whole organization.

The top-level totals are the sum across every live number: an organization with two numbers on a 50,000-message plan reports a quota of 100,000, not 50,000. The numbers[] breakdown shows each number separately, which is what you need to find the one that is close to its own ceiling, so a healthy-looking total can hide a number at 99%.

For one number, get_message_quota and get_contact_quota are more direct.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely non-obvious semantic: top-level totals are summed across every live number, so an org on a 50,000-message plan with two numbers reports 100,000. That aggregation rule is the kind of detail that prevents a serious misreading of the response, and it goes well beyond what the annotations say.

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?

Three short paragraphs, front-loaded with the org-wide scope before the aggregation caveat and the sibling redirect. The 50,000-vs-100,000 example is the one piece of apparent redundancy that clearly earns its place by making the summing rule concrete.

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

Completeness5/5

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

An output schema exists, so return values need not be described, yet the description still flags the key structural fact an agent needs — that `numbers[]` carries the per-number breakdown. For a zero-parameter, read-only tool this is fully sufficient.

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 there is no parameter meaning for the description to add; the baseline of 4 applies. Nothing in the description conflicts with or duplicates 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?

States a specific verb and resource ('Get WhatsApp message and contact usage') plus an explicit scope ('for the whole organization'). The scope clause is exactly what separates it from the per-number siblings get_message_quota and get_contact_quota, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Names the alternatives explicitly ('For one number, get_message_quota and get_contact_quota are more direct') and gives the condition that selects this tool instead: you need the org-wide view or the per-number breakdown. It also states the practical reason to prefer this tool — spotting a single number near its own ceiling.

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.