Skip to main content
Glama

Money alerts

money_alerts
Read-onlyIdempotent

Money alerts for one website: the alert rules (metric, condition, threshold, last reading against its expected band, open or not), the alerts that fired lately with the revenue at stake, and the channels they go to (kind and name only). Breakage alerts are in tracking_status.

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

Input Schema

NameRequiredDescriptionDefault
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context. It contributes the single-website scoping constraint, the shape of what is returned, and a deliberate narrowing ('kind and name only' for channels) that sets expectations about output depth, plus a cross-reference to tracking_status for breakage data.

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 carries the resource scope first, then the payload breakdown, then the sibling routing note — the most decision-relevant information comes first. Each parenthetical (metric/condition/threshold, 'kind and name only') adds real precision rather than restating the tool name.

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?

The tool is simple (one optional param) and has an output schema, so return-value documentation is not required; the description still sketches content well. The only shortfall is that 'alerts that fired lately' leaves the lookback window and volume unspecified, with no mention of any way to control it.

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 one parameter at 100% schema description coverage, the schema already explains that website_id accepts a uuid or domain and can be omitted for single-site accounts. The description only reinforces the single-website scope ('for one website') without adding format, defaulting, or resolution-order detail beyond the schema, so baseline 3 is appropriate.

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?

The description names the exact resource ('money alerts for one website') and enumerates its three payload sections: rule definitions (metric, condition, threshold, last reading vs expected band, open state), recently fired alerts with revenue at stake, and channels (kind and name only). It explicitly redirects breakage alerts to the sibling tracking_status, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

There is an explicit exclusion and routing rule: 'Breakage alerts are in tracking_status,' which tells the agent when NOT to use this tool and which alternative to pick. The positive case (use this for money/revenue-related alert rules and recent firings on a site) is strongly implied by the enumerated content, but never stated as a direct 'use when' clause.

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