MRR Ledger

Search businesses (start here)

search_businesses

Read-onlyIdempotent

Use when the user asks how much revenue, MRR or ARR an AI agent, AI startup or AI tool makes, or wants real examples of AI businesses in a niche (support, coding, voice, sales, SEO...). Returns AI-agent businesses with sourced, dated revenue (start here). Example: {"query":"support","limit":3} -> 3 customer-support agents with their sourced revenue. Each brief: slug, name, category, tier, one_liner, annualized_revenue_usd, basis, confidence, url_profile; + total + next page. Empty query = all, highest revenue first; filters category, tier, verified_only; limit max 50, offset/cursor. Next: get_business {"slug"}. Cost: free (100 calls/day without a key).

Input Schema

Name	Required	Description
`tier`	No	Funding-based, not size-based: venture = raised outside venture money (even if small), indie = bootstrapped/founder-funded, experiment = agent-run or research project.
`limit`	No	Results per page. Default 10, max 50.
`query`	No	Keyword, e.g. "support", "coding", "voice". Empty = all businesses.
`cursor`	No	Opaque page token: page.next_cursor from the previous call with the same query and filters.
`offset`	No	Skip this many matches (page start). Default 0. Use page.next_offset from the previous call.
`category`	No	Category slug, e.g. coding-agents, customer-support (see list_categories).
`verified_only`	No	Keep only businesses whose headline figure is payment-processor verified (headline_verification not null).

Output Schema

Name	Required	Description	Default
`page`	No	Pagination: call again with offset = next_offset (or cursor = next_cursor) while has_more.
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 20, 2026

addedInput schema / properties / category / description

Added value: +"Category slug, e.g. coding-agents, customer-support (see list_categories)."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque page token: page.next_cursor from the previous call with the same query and filters.",
+  "type": "string"
+}

addedInput schema / properties / limit / description

Added value: +"Results per page. Default 10, max 50."

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many matches (page start). Default 0. Use page.next_offset from the previous call.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / query / description

Added value: +"Keyword, e.g. \"support\", \"coding\", \"voice\". Empty = all businesses."

addedOutput schema / properties / page

Added value: +{
+  "additionalProperties": false,
+  "description": "Pagination: call again with offset = next_offset (or cursor = next_cursor) while has_more.",
+  "properties": {
+    "has_more": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "next_offset": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "offset": {
+      "type": "number"
+    },
+    "returned": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "offset",
+    "limit",
+    "has_more",
+    "next_offset",
+    "next_cursor"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedOct 20, 2026

addedOutput schema / properties / result / items / properties / referral
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / result / items / properties / signup_go_url

Added value: +{
+  "description": "Same link via mrrledger.com/go/<slug> (counts the click, then 302)",
+  "type": "string"
+}

addedOutput schema / properties / result / items / properties / signup_url

Added value: +{
+  "description": "Referral link (only on businesses with one). Always shown with signup_url_disclosure; never affects figures, ranking, sorting or verification.",
+  "type": "string"
+}

addedOutput schema / properties / result / items / properties / signup_url_disclosure
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / result / items / properties / signup_url_label
```
Added value: +{
+  "type": "string"
+}
```

First observedOct 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: cost model (free, 100 calls/day without a key), default sort behavior (highest revenue first when query is empty), and pagination fields (total, next page). It stops short of saying what confidence tiers or basis values mean, but that is minor.

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?

Front-loaded with the trigger sentence and example, with the field list and pagination details compactly packed. Dense but every clause carries information; the enumerated field list is slightly bulky given an output schema exists.

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?

For a 7-param search tool with full schema coverage, annotations, and an output schema, the description supplies the trigger, the example, sort defaults, cost limits, and the recommended next call. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3; the description still adds semantics the schema lacks, notably default sort order (highest revenue first on empty query), the empty-query-means-all convention, and a worked example with limit. It doesn't explain cursor vs offset precedence, which the schema only partially covers.

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?

Specific verb+resource with an explicit scope statement: it returns AI-agent businesses with sourced, dated revenue, and the title/description both say 'start here'. It clearly separates itself from siblings by naming get_business as the follow-up and list_categories for category slugs.

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?

Opens with an explicit trigger ('Use when the user asks how much revenue, MRR or ARR...or wants real examples of AI businesses in a niche'), then names the next step (get_business {"slug"}) and points to list_categories for slugs. An agent knows both when to call it and what to call afterward.

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

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