Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get a number's message quota for this billing cycle

get_message_quota
Read-onlyIdempotent

Check how much of this WhatsApp number's message allowance is left.

The quota is per number, not per organization: an organization with three numbers has three separate allowances. It resets at cycle_end, which is the organization's real billing boundary rather than a rolling window, so resets_at is a date you can plan around.

Only messages sent through Turbo Notify consume it. Messages someone sends from the phone itself do not.

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_message_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description doesn't need to restate safety. It does add genuine behavioral context beyond that: quota is scoped per number, resets on a real billing boundary rather than a rolling window, and only Turbo Notify traffic draws it down. It stops short of mentioning any limits at zero quota or auth requirements.

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?

Three short paragraphs, front-loaded with the core purpose followed by scope and reset semantics. Structure is clean, though the reset paragraph is slightly wordier than needed with the bold and inline-code emphasis on `cycle_end` and `resets_at`.

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 single-parameter, read-only tool with an output schema covering return values, the description supplies the key semantic context an agent would otherwise lack. The one remaining gap is the absence of routing to adjacent tools like get_contact_quota or get_usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the number_alias parameter is already fully documented in the schema, including the alias-vs-id distinction and the list_numbers pointer. The description only reinforces the per-number scoping and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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?

Opens with a concrete verb and resource: check how much of this WhatsApp number's message allowance is left. The following sentences sharpen the scope (per number, not per organization) so an agent can immediately tell it apart from a contact-quota or general-usage tool.

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?

Usage is only implied: the tool is for gauging remaining allowance and planning around the reset date. No explicit when-to-use or when-not guidance, and no routing toward near siblings such as get_usage or get_contact_quota, so the agent has to infer the distinction.

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.