Skip to main content
Glama

MRR Ledger

by com.mrrledger
OverviewDiscussionsAdmin

Benchmark your MRR against category peers

benchmark_business
Read-onlyIdempotent

Use when the user gives their own MRR or asks whether their revenue is good compared with similar AI businesses. Returns where an MRR ranks among fresh same-category MRR peers (rank of N + 1 comparable). Example: {"category":"customer-support","mrr":2000} -> your rank among the customer-support MRR peers + 1 comparable. Also: N, basis, verification date, peer caveat; no growth numbers yet; your MRR is never stored. Cost: free (100 calls/day without a key).

Input Schema

NameRequiredDescriptionDefault
mrrYesYour monthly recurring revenue in USD, e.g. 2000 (greater than 0, at most 100000000). Not stored.
fullNoFull answers are paused (paid tier paused while we confirm source permissions); you get the free answer.
categoryYesCategory slug, e.g. customer-support, automation-platforms, sales-gtm, indie-solo (see list_categories).
months_liveNoOptional months since launch (0-600). Accepted but ignored for now.
report_tokenNoNot used while the paid tier is paused.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / full / description
      Previous value: -"true = ask for the full answer (needs a Builder/Team/Pro key or a Verified Snapshot token; otherwise you get the free answer plus how to unlock)."New value: +"Full answers are paused (paid tier paused while we confirm source permissions); you get the free answer."
    • changedInput schema / properties / report_token / description
      Previous value: -"Optional: the 48-hex token from a $9 Verified Snapshot purchase (unlocks full answers for every category for its 7-day window; an earlier Category Report token: its category)."New value: +"Not used while the paid tier is paused."
  2. Changed2 schema fields changed
    • changedInput schema / properties / full / description
      Previous value: -"true = ask for the full answer (needs a Builder/Team/Pro key or a Verified Snapshot / Data Licence token; otherwise you get the free answer plus how to unlock)."New value: +"true = ask for the full answer (needs a Builder/Team/Pro key or a Verified Snapshot token; otherwise you get the free answer plus how to unlock)."
    • changedInput schema / properties / report_token / description
      Previous value: -"Optional: the 48-hex token from a $9 Verified Snapshot or Data Licence purchase (unlocks full answers for every category for its 7-day window; an earlier Category Report token: its category)."New value: +"Optional: the 48-hex token from a $9 Verified Snapshot purchase (unlocks full answers for every category for its 7-day window; an earlier Category Report token: its category)."
  3. Changed2 schema fields changed
    • changedInput schema / properties / full / description
      Previous value: -"true = ask for the full answer (needs a Builder/Team/Pro key or a Category Report token for this category; otherwise you get the free answer plus how to unlock)."New value: +"true = ask for the full answer (needs a Builder/Team/Pro key or a Verified Snapshot / Data Licence token; otherwise you get the free answer plus how to unlock)."
    • changedInput schema / properties / report_token / description
      Previous value: -"Optional: the 48-hex token from a Category Report for this category (unlocks full answers for its 7-day window)."New value: +"Optional: the 48-hex token from a $9 Verified Snapshot or Data Licence purchase (unlocks full answers for every category for its 7-day window; an earlier Category Report token: its category)."
  4. Added

TDQS

A4.5/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 behavior, and the description adds meaningful context beyond them: no storage of MRR, free usage with a daily cap, lack of growth numbers, and peer caveats. This is unusually transparent for a benchmark tool.

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?

Front-loads the use case, then gives the return shape, caveats, and cost without padding. Every sentence contributes useful selection or invocation context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema coverage, existing output schema, and informative annotations, the description is complete enough for an agent to call correctly. It covers scope, limitations, cost, privacy, and output expectations.

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 description coverage is 100%, so the parameter definitions already do the heavy lifting. The description adds an example input mapping but does not explain the optional parameters or add semantics beyond the schema, making the baseline 3 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?

States a specific verb and resource: benchmarking the user's MRR against same-category peers. The example and the "rank of N + 1 comparable" phrase make the returned concept concrete, so an agent can distinguish it from generic business lookup or growth tools.

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?

Explicitly says to use it when the user provides their own MRR or asks whether revenue is good versus similar AI businesses. It does not name alternatives or exclusions, but the user-supplied MRR condition is a clear routing cue.

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

All MRR Ledger 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