Skip to main content
Glama
Sign In

Anry

by io.anry.mcp
OverviewDiscussionsAdmin

Get revenue leaks

get_revenue_leaks
Read-onlyIdempotent

The flagship money call: the site's deduplicated revenue (or users) at risk per week and month, plus the top 5 active leaks ranked by weekly potential loss with impact levels. Use for 'where are we losing money' and to pick what to fix first. Quote monetary values verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "get_revenue_leaks"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesSite id from list_sites (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses deduplication, weekly and monthly aggregation, a top-five active-leak limit, ranking by weekly potential loss, and impact levels. 'Quote monetary values verbatim' adds useful response-handling guidance, though the condition governing revenue versus users is unexplained.

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 compact sentences front-load the returned information, then provide selection triggers and a monetary quoting rule. 'Flagship money call' is mildly promotional, but the description otherwise packs substantial operational detail into very little text.

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 one-parameter read with no output schema, it covers scope, measures, time windows, result count, ordering, impact levels, and prioritization use. The unresolved 'revenue (or users)' wording leaves a material ambiguity about which mode applies and when.

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?

The sole parameter is fully documented in the schema as a 36-character site UUID obtained from list_sites. The description confirms site scope but adds no parameter syntax or sourcing beyond that, so the high-coverage 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?

It identifies a site-scoped read of deduplicated revenue or users at risk, plus the top five active leaks, with weekly/monthly horizons and a clear ranking basis. This specific money-loss and prioritization scope distinguishes it in substance from general analytics, paid-waste, and opportunity-listing siblings.

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?

It explicitly routes 'where are we losing money' questions and decisions about what to fix first to this tool. Although it names no sibling alternative, these two concrete triggers make selection straightforward.

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

All Anry toolsInspect
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