Skip to main content
Glama

Ready4Bots

by com.ready4bots
OverviewDiscussionsAdmin

Search businesses

search_businesses
Read-onlyIdempotent

Search the public Ready4Bots index. Free text matches name, industry, tags, product keywords, category, description, and domain, including synonyms such as shoes/sneakers, coffee/espresso, and hotel/lodging. Results are ranked by that relevance, then by published R-level. Filter by category (E-commerce, SaaS, or an industry id such as fashion-shoes), country, exact level (R0–R3 from a published test, R4 only for the certified seal), minimum level, action (search, book, or order), audience (customer, seller, or dev), and certified. The response includes totalIndexed, the size of the catalog, and indexSource. Each result includes level, status, certified, industry, channel, actions, audience, sourceUrl, and ready4botsUrl. A level is present only when a test recorded one. Unverified listings are never certified. The tool waits for the live providers table. indexSource is postgres when that read finishes, including when it returns no public row. indexSource is snapshot, with fallbackReason, only when the database cannot be reached. get_business reads the same catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoExact published level. R0–R3 are test levels. R4 is the Verified Agent Purchase umbrella. R4-N and R4-W are the two seals. No business has R4 yet.
limitNoPage size. Default 20, max 50.
queryNoFree text matched against name, industry, tags, product keywords, category, description, country, id, and domain. shoes matches sneakers, coffee matches espresso, hotel matches lodging.
actionNoPublished action: search (product search with prices), book (reservation), or order (cart and checkout).
offsetNoNumber of matches to skip.
countryNoCountry code stored on the listing, for example DE or US.
audienceNocustomer when a customer action is published. seller and dev are not in this index and return no rows.
categoryNoChannel or industry id, for example SaaS, E-commerce, or coffee-food-drink.
certifiedNotrue keeps only the Ready4Bots certified seal. false drops sealed listings.
min_levelNoKeep listings whose published level is at least this. Unscored listings are omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / level / description
      Previous value: -"Exact published level. R0–R3 are test levels. R4 is the certified seal only."New value: +"Exact published level. R0–R3 are test levels. R4 is the Verified Agent Purchase umbrella. R4-N and R4-W are the two seals. No business has R4 yet."
    • changedInput schema / properties / level / enum
      Previous value: -[
-  "R0",
-  "R1",
-  "R2",
-  "R3",
-  "R4"
-]New value: +[
+  "R0",
+  "R1",
+  "R2",
+  "R3",
+  "R4",
+  "R4-N",
+  "R4-W"
+]
    • changedInput schema / properties / min_level / enum
      Previous value: -[
-  "R0",
-  "R1",
-  "R2",
-  "R3",
-  "R4"
-]New value: +[
+  "R0",
+  "R1",
+  "R2",
+  "R3",
+  "R4",
+  "R4-N",
+  "R4-W"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly, idempotent, non-destructive). It discloses ranking order (relevance then published R-level), that unverified listings are never certified, that levels appear only when a test recorded one, and a detailed indexSource contract covering the live postgres read and the snapshot/fallbackReason path when the DB is unreachable. This is exactly the operational context annotations cannot carry.

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-loads the purpose and ranking model before the parameter recap, and most sentences earn their place by describing behavior not visible in structured fields. It runs long and repeats the synonym examples already present in the query parameter, which keeps it from a 5.

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 no output schema, the description fully compensates by naming the response envelope (totalIndexed, indexSource) and the per-result fields (level, status, certified, industry, channel, actions, audience, sourceUrl, ready4botsUrl). Combined with the indexSource fallback semantics, an agent has everything needed to call and interpret the tool.

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 schema already documents all ten parameters including the enums and synonyms. The description reiterates the filter surface but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('Search the public Ready4Bots index') and immediately scopes what is searched (name, industry, tags, product keywords, category, description, domain). It also distinguishes itself from the sibling get_business by noting they read the same catalog, so an agent can route between search vs lookup.

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?

Provides strong context on how results are ranked and enumerates every filterable dimension, which tells the agent when this tool fits. However, it never explicitly contrasts when to use this versus the sibling get_business beyond a single closing sentence, and offers no exclusions or prerequisites.

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

All Ready4Bots 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