MRR Bench Pricing

search_tools

Search SaaS/AI tools by name or category in the MRR Bench index (4,164 tools with verified pricing).

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": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	Tool name or keyword, e.g. 'jennifer' or 'seo'

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the corpus size and that pricing is verified, signaling a curated index rather than live data, but says nothing about result ordering, whether the search is exact vs fuzzy, or what a hit contains.

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 with zero filler; the identifying scope and corpus size appear immediately.

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

Completeness3/5

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

For a two-parameter search with no output schema, the definition covers what the index is but not what comes back or how limit affects response shape. Adequate to invoke correctly, thin for interpreting results.

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 50%: the query parameter is documented in the schema, while limit is not. The description adds 'by category', extending query semantics slightly beyond the schema's 'Tool name or keyword', but gives no help on limit — the unannotated maximum of 50 and default of 10 remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Search SaaS/AI tools') plus a scoped corpus ('MRR Bench index, 4,164 tools with verified pricing'), which is enough to distinguish it from get_pricing/price_changes/stack_cost by function. It stops short of explicitly naming what those siblings do, so the differentiation is inferred rather than stated.

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?

'By name or category' implies the intended lookup patterns, which is usable guidance for an agent. However, there is no explicit when-to-use framing, no mention of how it pairs with get_pricing or stack_cost (e.g., find a tool first, then price it), and no exclusions.

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

All MRR Bench Pricing 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.