Skip to main content
Glama

Get Event

get_event
Read-only

Get one public Moments event by its UUID from search_events: title, time, venue, price, event page URL and a short description excerpt. Data is public Moments event listings for Norwegian and other cities. Event texts come from third-party organizers.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesUUID of the event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this a read-only, non-open-world lookup, so the safety profile is covered. The description adds real context beyond that: the corpus is public Moments listings for Norwegian and other cities, texts originate from third-party organizers (a reliability caveat), and the description field is only an excerpt. It does not discuss behavior for a missing/unknown UUID or error handling.

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 tight sentences, front-loaded with the action and identifier, then the payload, then provenance. The final sentence about third-party organizer texts is the least essential but still supports interpreting the returned content, so nothing is truly wasted.

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 read tool with no output schema, the description supplies the returned field list, the data source, and the truncation caveat on the excerpt. An agent has everything needed to call it correctly and interpret the result.

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, but the description adds a genuine constraint beyond the schema's 'UUID of the event': the identifier is expected to come from a prior search_events call rather than being constructed. That provenance guidance is the only additional meaning available for a single parameter.

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 one public Moments event) keyed by UUID, and enumerates what comes back: title, time, venue, price, event page URL, description excerpt. It also ties the identifier to search_events, so an agent can distinguish this from the listing sibling without opening the schema.

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?

The phrase 'by its UUID from search_events' makes the prerequisite chain clear: search_events first, then this tool for a single event's detail. It stops short of an explicit 'do not use for listing/browsing' exclusion or any mention of list_cities, so the routing guidance is clear but not exhaustive.

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.

Resources