Skip to main content
Glama
Sign In

Selfe

by ai.selfe
OverviewDiscussionsAdmin

match_venues

Read-onlyIdempotent

Get full details for places the user already means — by id (from discover_venues) or by name, with an optional website and town to tell same-named places apart. Pass stay to get live rooms and offers whose offer ids go straight to book_venue. A name that fits several places returns candidates: ask the user which, never guess. Structured JSON, not a rendered UI.

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": {
      "places": "<places>"
    },
    "name": "match_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
stayNoWhen given, each matched place carries its live rooms and offers for these dates and party.
placesYesThe places to match: ids, or a name with optional website and location.
renderNoAsk for layout hints alongside the results. Delivery (one body or a stream) is chosen by the Accept header, not here.
projectionNo`detail` (default) is the full record; `listing` is the compact card a list page needs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is supplementary — and it delivers by disclosing the ambiguity outcome (candidates instead of a guess) and the availability semantics of `stay`. The only soft spot is "Structured JSON, not a rendered UI," which sits in mild tension with the `render.a2ui` option in the schema.

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?

Four compact sentences, front-loaded with purpose then input forms then the ambiguity rule. Dense with em-dashes but every clause carries information; nothing reads as filler.

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?

For a tool with nested `stay`, an anyOf `places` array, and no output schema, the description covers the important contract: what comes back, how ambiguity is surfaced, and how offer ids chain to booking. A brief note on listing vs detail output would close the remaining gap.

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; the description earns more by explaining what `stay` actually produces (live rooms and offers whose ids feed book_venue) and why `website`/`town` exist (telling same-named places apart). `projection` and `render` are not explained, which keeps it off a 5.

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 ("Get full details for places") and immediately scopes the input form: by id from discover_venues or by name with disambiguators. This clearly separates it from discover_venues (finding places) and book_venue (booking them).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: obtain ids from discover_venues, pass `stay` when live rooms and offers are wanted, and send offer ids onward to book_venue. It also gives an exclusion-style rule for the ambiguous case — return candidates and ask the user, never guess.

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

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