The Revenue AI Report

Search the AI tool library

search_tools

Read-onlyIdempotent

Search The Revenue AI Report AI tool library: go-to-market and revenue AI vendors with category, revenue functions, use cases, adoption effort level, and vendor claims. Ranking runs on name, description, best-for, and use cases; vendor keywords only count on an exact whole-tag match, so a generic word does not pull in unrelated vendors. Filter with category, revenueFunction, maturity (L1 to L6), or tag. Every response returns availableFilters with the full category and revenue-function lists plus the most common vendor tags, so you can re-run a narrowed query without guessing the taxonomy. Vendor claims are the vendor's own, not Report benchmarks.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Exact vendor keyword, for example 'forecasting'. See availableFilters.topTags.
`limit`	No	Default 25.
`query`	No	Keyword matched on name, description, best-for, and use cases, ranked by relevance.
`category`	No	Exact tool category, for example 'Productivity & Automation'. See availableFilters.categories.
`maturity`	No	AI maturity level, from L1 Starter to L6 Rebuilt.
`revenueFunction`	No	Exact revenue function, for example Sales, Marketing, Customer Success, Revenue Operations. See availableFilters.functions.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`tools`	Yes
`total`	Yes
`matched`	Yes
`returned`	Yes
`adoptionLevels`	Yes
`availableFilters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026

changedInput schema / properties / maturity / description

Previous value: -"Adoption effort level, 1 (one seat, no workflow change) to 5 (agent runs the work, human audits)."New value: +"AI maturity level, from L1 Starter to L6 Rebuilt."

changedInput schema / properties / maturity / maximum
```
Previous value: -5New value: +6
```

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "adoptionLevels": {},
+    "availableFilters": {
+      "additionalProperties": {},
+      "properties": {
+        "categories": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "functions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "maturity": {
+          "items": {
+            "type": "number"
+          },
+          "type": "array"
+        },
+        "topTags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "categories",
+        "functions",
+        "maturity",
+        "topTags"
+      ],
+      "type": "object"
+    },
+    "matched": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    },
+    "returned": {
+      "type": "number"
+    },
+    "tools": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "functions": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "maturity": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "website": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "category",
+          "description",
+          "functions",
+          "maturity",
+          "website",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "matched",
+    "returned",
+    "tools",
+    "adoptionLevels",
+    "availableFilters",
+    "note"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: ranking runs on name, description, best-for, and use cases; vendor keywords only match on exact whole-tag matches; every response returns availableFilters; and vendor claims are self-reported, not Report benchmarks. This meaningfully enriches the readOnly/idempotent/destructive annotations.

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?

The description is dense but well-organized, with the core purpose front-loaded and supporting behavioral caveats following in logical order. No sentence is wasted, though the first sentence somewhat restates the title and the overall length is at the higher end for a search tool.

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?

With a rich output schema, 100% schema parameter coverage, and strong annotations, the description covers everything an agent needs to invoke the tool correctly: search behavior, filtering mechanics, exact-match caveats, availableFilters, and a data provenance warning. There are no significant gaps.

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 the baseline is 3, but the description adds real semantic value: it explains that tag matches must be exact whole-tag matches, query ranking applies to specific fields, and maturity maps to L1–L6 levels. This goes beyond the schema's individual field descriptions.

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 clearly states the tool searches 'The Revenue AI Report AI tool library' for go-to-market and revenue AI vendors, with specific dimensions like category, revenue functions, and use cases. It is specific about the resource and action, but it does not explicitly differentiate itself from sibling tools like search_publications or search_site, so it falls just short of a 5.

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?

The description gives clear context on how to use the tool: filter by category, revenueFunction, maturity, or tag, and leverage availableFilters to refine queries without guessing the taxonomy. It does not explicitly state when to use this tool instead of alternatives such as get_tool or list_tools, so it lacks explicit exclusion guidance.

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

All The Revenue AI Report 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?