Skip to main content
Glama

Money leaks

money_leaks
Read-onlyIdempotent

Revenue leaks for one website ranked by money at risk over the last 28 finalized Search Console days: weak snippets and positions against the CTR curve, keyword cannibalisation, checkouts started but not paid, and 404s getting search clicks. Each leak is lost visits x revenue per visit, with its basis (estimate, or upper_bound when it assumes every lost visit would have paid), confidence and one fix. Amounts are minor units of currency (cents for usd, whole yen for jpy).

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

Input Schema

NameRequiredDescriptionDefault
limitNoleaks to return, 1-50; default 20
currencyNolowercase ISO 4217 code; default the website's main currency
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.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the description's job is to add analytical context — and it does: the fixed 28-finalized-day window (signalling data lag), the exact loss formula ('lost visits x revenue per visit'), the meaning of the 'basis' field including when it is an upper_bound, and that each leak carries confidence plus one fix. It also states the currency unit convention (minor units, with the jpy exception), which prevents a 100x misread of returned amounts.

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?

Two sentences: the first front-loads scope, ranking and the leak taxonomy; the second handles the money semantics. Dense but every clause carries information, with no filler or repetition of the schema. The first sentence is long and comma-stacked, which slightly slows parsing.

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 fairly complex analytical tool with an output schema already documenting the return shape, the description supplies the domain framing an agent needs: what counts as a leak, how the amount is derived, and what the basis/confidence fields mean. Minor gaps remain — behaviour when no leaks are found, and how 'finalized' days differ from current data — but nothing essential to correct invocation is missing.

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?

Schema coverage is 100% and all three parameters are documented inline (limit 1-50 default 20, lowercase ISO 4217 currency defaulting to the site's main currency, website_id as uuid or domain, omittable for single-site accounts). The description adds only indirect meaning — 'for one website' and the cents/whole-yen convention tied to currency — so the baseline 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?

The description names a specific resource and scope: 'Revenue leaks for one website ranked by money at risk over the last 28 finalized Search Console days', then enumerates the four leak categories (CTR-curve gaps, cannibalisation, unpaid checkouts, 404s with search clicks). That level of detail makes it unmistakable against alerting or generic-insight siblings such as money_alerts or insights.

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 implied rather than stated: the agent can infer this is the tool for 'what is costing me money on this site', and the 28-day window is fixed. But there is no explicit when-to-use/when-not guidance, no named alternative (e.g. money_alerts for monitoring vs. this for diagnosis), and no prerequisites such as needing Search Console connected.

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