get_event_details
Get fuller public details for one discoverable EventMatey event, including the canonical hosted booking URL.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes | EventMatey event UUID |
EventMatey Event Discovery
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that results include 'fuller public details' and a booking URL, but does not mention authentication needs, error behavior, or data limits.
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?
The description is a single concise sentence that efficiently conveys the tool's purpose without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool (one parameter, no output schema), the description is minimally adequate but could be improved by listing the types of details returned or covering error cases.
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?
The schema already fully describes the single parameter (event_id as a UUID), so the description adds no additional parameter semantics. Baseline 3 is appropriate.
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?
The description clearly states the tool fetches 'fuller public details for one discoverable EventMatey event' including the booking URL. It distinguishes from sibling search tools by focusing on a single event's details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is used after discovering an event via search tools, but does not explicitly state when to use it vs alternatives or provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a distinct purpose: get_event_details retrieves details for a specific event, search_events_by_keyword enables keyword-based search, and search_events_nearby is location-focused. No overlap in primary functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: get_event_details, search_events_by_keyword, search_events_nearby. The verbs (get, search) are appropriate for the actions and are uniformly used.
Tool Count5/5
Three tools is an appropriate and well-scoped set for an event discovery service, covering detail retrieval and two distinct search methods without unnecessary redundancy.
Completeness4/5
Core discovery operations are covered: keyword search, location search, and event details. Minor gap is absence of a tool to list available filter options (e.g., categories), but overall surface is sufficient for typical use cases.