GreatWait

Read billing notification settings

billing_notificationsettings

Read-onlyIdempotent

Reads the low-credit threshold in effect and the optional-email choice. Unless a threshold was chosen, it is one fifth of the organization's most recent credit purchase or grant, rounded down to a whole cent, and zero before any credit was granted. Critical email remains mandatory for owners and active billing-role members; addresses and contact management are absent.

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": "billing_notificationsettings"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`revision`	Yes
`freshness`	Yes
`recipients`	Yes
`criticalEmail`	Yes
`noncriticalEmail`	Yes
`lowCreditThreshold`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so safety is known. The description adds genuine non-obvious behavior: the default threshold derivation (one fifth of the most recent purchase or grant, rounded down, zero before any grant) and that critical email is mandatory for owners and active billing-role members.

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 sentences with the operation front-loaded and the default-value nuance following. It is dense but every clause carries information an agent needs to interpret the result; the trailing 'addresses and contact management are absent' is a slightly oblique note but still scoping.

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 no-arg read tool with an output schema present, the description need not restate return fields, and it usefully explains what the values mean when unset plus what is deliberately omitted. Only the lack of sibling routing keeps it from being fully complete.

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?

Zero input parameters, so the baseline is 4. There is nothing for the description to clarify about arguments, and it correctly focuses on the returned semantics instead.

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?

States a specific verb ('Reads') and resource ('billing notification settings'), then enumerates the exact contents returned (low-credit threshold, optional-email choice). It is not a tautology of the title, but it never explicitly contrasts itself with the sibling billing_notificationsettingsupdate.

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?

No statement of when to use this read tool versus the update counterpart or billing_notices. The presence of billing_notificationsettingsupdate makes the omission of a routing hint a real gap, though read-only intent is implied by the verb.

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

All GreatWait tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?