Excellent Reference (free)

Find venues that take inquiries from assistants

find_event_venues

Read-onlyIdempotent

Finds restaurants and venues on Excellent that accept private-event and group-dining inquiries from AI assistants, by the restaurant group's or the venue's name. Returns up to 10, each with the group, the venue, who replies, a handle for send_event_inquiry and the venue's public inquiry page. Only venues that opted in are listed, and only what their public inquiry page shows. No account needed.

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": "find_event_venues"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The restaurant group's or venue's name, e.g. "Lumière" or "Harbor Room".

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real substance beyond them: a result cap of 10, that only opted-in venues appear, and that only publicly visible inquiry-page data is exposed — useful expectations about selectivity and data provenance.

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?

Three dense sentences, front-loaded with the purpose, then the return shape, then eligibility and auth caveats. Every clause carries information; no filler or repetition of the title.

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 one-parameter, non-destructive lookup with no output schema, the description supplies what matters: result limit, return fields, eligibility restriction, data source, and no-auth status. Nothing an agent needs to call 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% and the parameter description already gives examples, so the baseline is 3. The description adds the meaningful constraint that the query is a group or venue NAME (not cuisine, location, or free text), which prevents an agent from passing a topical search string.

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 ('Finds restaurants and venues on Excellent that accept private-event and group-dining inquiries'), plus the lookup key ('by the restaurant group's or the venue's name'). The scope — assistant-originated inquiries, opted-in venues — clearly separates it from search_excellent_pages and positions send_event_inquiry as the downstream step.

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?

Gives clear context for use: name-based lookup, and the returned handle feeds send_event_inquiry, which implicitly tells the agent this is the discovery half of an inquiry flow. It also notes 'No account needed,' removing an auth prerequisite question. It stops short of explicitly naming when NOT to use it versus search_excellent_pages.

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

All Excellent Reference (free) 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?