RoloCache

lookup_vendors

Search the RoloCache catalog and return matching vendors.

All three parameters are optional and combinable. With no parameters, returns all indexed vendors.

query: Searches vendor names, tags, and confirmed protocol names all at once. Examples: "hotel", "car rental", "corporate travel", "MCP". Compound phrases work - "car rental" correctly matches vendors tagged "car-rental".

protocol: Exact match against confirmed protocol names. Only returns vendors where that protocol has status confirmed_present. Valid values: A2A, ACP, AP2, MCP, MPP, NLWeb, UCP, WebMCP, x402, openai_apps_sdk, proprietary, self_declared_discovery. An unrecognized value returns empty results, not an error.

has_agent_interface: Exact match against "true", "false", or "partial". "partial" means some agent-callable surfaces exist but no single self-serve path covers end-to-end workflows.

Results only include vendors with real, current scan data. Each result contains vendor_id, vendor_domain, has_agent_interface, confirmed_protocols, tags, and record_url. Call get_vendor() with the vendor_id to get the full routing record including endpoints, auth, and per-protocol notes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`protocol`	No
`has_agent_interface`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description fully covers behavior: search semantics, protocol exact match, has_agent_interface values, result inclusion criteria, and suggested follow-up via get_vendor().

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?

Well-structured: one-sentence purpose, then parameter details with examples. No fluff, every sentence is informative.

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

Completeness4/5

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

Comprehensive for a search tool: lists result fields and suggests follow-up. Could mention pagination or limits, but not necessary given the context. Output schema exists but not shown; description covers output sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description provides detailed semantics for each parameter: query examples, protocol valid values and behavior, has_agent_interface meaning of 'partial'. Greatly enriches the schema.

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?

Starts with clear verb+resource: 'Search the RoloCache catalog and return matching vendors.' Distinguishes from siblings like get_vendor which retrieves a single record.

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?

Explains all parameters are optional and combinable, including the no-parameter case returning all vendors. Does not explicitly contrast with siblings but context signals make the distinction clear.

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

All RoloCache tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a distinct role: get_catalog_info provides metadata, lookup_vendors searches vendors, get_vendor retrieves full records, and report_to_outpost submits feedback. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores: get_catalog_info, get_vendor, lookup_vendors, report_to_outpost.

Tool Count4/5

Four tools cover the core workflow of exploring, searching, retrieving details, and reporting. Slightly on the low side but well-scoped for a catalog/feedback system.

Completeness4/5

The tool surface covers discovery, search, detail retrieval, and feedback. Missing update/create capabilities, but those appear out of scope for this read-oriented catalog.

Resources

Need Help?