tickadoo Experiences and Events

ask_theatre_concierge

Read-onlyIdempotent

Use this when the user asks a free-text theatre question (best musical for kids, romantic show tonight, cheap comedy). Returns a concise grounded answer plus cited theatre products with booking URLs. Intent-aware (budget, audience, timeframe) via the concierge seam.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ask_theatre_concierge"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	City name, resolved to a slug.
`limit`	No	Max cited products. Defaults to 5.
`format`	No	Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.	json
`language`	No	BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
`question`	No	Free-text theatre question, max 500 chars.
`city_slug`	No	City slug, e.g. london.

Output Schema

Name	Required	Description	Default
`answer`	No
`detail`	No
`message`	No
`question`	No
`city_slug`	No
`error_type`	No
`cited_products`	No
`schema_version`	No
`detected_intents`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. The description adds real context beyond them: it returns a concise grounded answer plus cited products with booking URLs, and is intent-aware across budget/audience/timeframe. It omits latency or grounding-source caveats, but the annotation bar is low and this exceeds it.

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?

Three compact sentences, front-loaded with the triggering condition, then output shape, then the intent-handling note. Little waste, though the trailing 'via the concierge seam' is internal jargon of marginal value to an agent.

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?

With an output schema present, return values need not be explained, and the description still characterizes the output (concise grounded answer + cited products with booking URLs). Combined with the clear trigger and annotations, an agent has what it needs to call it, missing only explicit sibling routing.

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 coverage is 100%, so the schema fully documents city, city_slug, limit, format, language, and question. The description adds only the abstract notion of intent-awareness (budget, audience, timeframe), which maps to the free-text question rather than adding concrete parameter-level meaning. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb ('asks a free-text theatre question') and resource, and illustrates with concrete examples (best musical for kids, romantic show tonight, cheap comedy). It is clearly the natural-language Q&A entry point versus the structured search/recommend siblings, though it never names those alternatives explicitly.

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?

It states a clear trigger ('Use this when the user asks a free-text theatre question') and reinforces it with examples. However, it offers no when-not guidance or routing to siblings like search_experiences, find_theatre_for_occasion, or get_show_guide, so the agent must infer boundaries.

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

All tickadoo Experiences and Events 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.