Skip to main content
Glama

Get a public event

get_public_event
Read-onlyIdempotent

Public details of an event on ticketick.ch: full description, upcoming sessions, ticket prices, availability and booking link. No API key needed.

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": {
      "slug": "<slug>"
    },
    "name": "get_public_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesEvent slug, from search_events.
localeNo

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit for adding what annotations cannot: that authentication is not required and what the response contains (sessions, prices, availability, booking link), which is valuable given there is no output 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?

Two short sentences, payload contents front-loaded, with the access note trailing. Nothing is padded, though the list form is slightly dense rather than maximally readable.

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 two-parameter read tool with no output schema, the description covers the essentials: what is fetched, what comes back, and that no key is required. Remaining gaps (locale behavior, price currency, behavior for unknown slugs) are modest.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: slug is documented in the schema as coming from search_events, but locale has an enum with no explanation anywhere. The description says nothing about either parameter and does not clarify that locale governs the language of the returned content.

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?

Names the resource precisely (a public event on ticketick.ch) and enumerates the payload: description, sessions, prices, availability, booking link. The only gap is that it never contrasts itself with the sibling search_events, which the schema field description does instead.

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?

Usage is only implied — the agent infers this is the single-event lookup versus search_events, and 'No API key needed' hints at access conditions. There is no explicit when-to-use/when-not statement or named alternative in the description itself.

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