Skip to main content
Glama

Event details

get_event
Read-onlyIdempotent

Everything about one event: description, every date with its ticket types and prices (PKR), venue, what is included, rules, FAQs, age limit and the booking link.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe event id from search_events, or its shapargullay.com/events/<id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds real value by disclosing the shape of the payload (per-date ticket types, PKR pricing, rules, FAQs, booking link) in the absence of an output schema; it only omits what happens with an unknown or expired id.

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?

A single dense sentence that front-loads the scope ('Everything about one event') and then enumerates fields. Nothing is wasted, though the long comma chain of return fields reads as a run-on and could be trimmed or grouped.

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 simple single-id lookup with full annotation coverage and a fully documented parameter, the description supplies enough to call it correctly and to know what comes back. Only error behaviour for a missing event id is left unexplained, which is minor at this complexity.

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?

There is a single parameter with 100% schema description coverage, and that schema entry already explains both the bare id and the shapargullay.com/events/<id> URL form. The description adds no additional parameter meaning, so the high-coverage baseline of 3 applies.

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 names the resource precisely ('one event') and enumerates exactly what is returned: description, dates with ticket types and prices in PKR, venue, inclusions, rules, FAQs, age limit and booking link. It is a contents list rather than a verb phrase and never names search_events as the contrasting discovery tool, so it falls short of a 5 that would fully separate it from siblings.

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

Usage Guidelines2/5

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

The description contains no when-to-use, when-not-to-use, or alternative-tool guidance. A flow is only inferable from the schema's id description ('from search_events'), which is structured data rather than the description itself, so the reader gets no explicit routing instruction.

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