Skip to main content
Glama

Event details / Szczegóły imprezy

get_event
Read-onlyIdempotent

One event on GdzieZabawa.pl by its id (slug) or page URL: name, next date and time, place, municipality, admission, description, further dates and the source website. / Szczegóły jednej imprezy.

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": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEvent id (slug) from search_events.
urlNoEvent page URL exactly as returned by search_events (format https://gdziezabawa.pl/wydarzenie/<id>).

Output Schema

NameRequiredDescriptionDefault
okYestrue = the tool ran, also when nothing was found (read status); false only for invalid_request, invalid_range, missing_argument or temporary_error.
noteNoGuidance for answering, e.g. when nothing was found.
eventNo
statusYes
messageNo
examplesNoExample values when a required argument was missing.
adjustmentsNoHow the server interpreted or ignored arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Event page URL, e.g. https://gdziezabawa.pl/wydarzenie/dni-skawiny"New value: +"Event page URL exactly as returned by search_events (format https://gdziezabawa.pl/wydarzenie/<id>)."
    • addedOutput schema / properties / ok / description
      Added value: +"true = the tool ran, also when nothing was found (read status); false only for invalid_request, invalid_range, missing_argument or temporary_error."
  2. Changed3 schema fields changed
    • addedOutput schema / properties / adjustments
      Added value: +{
      +  "description": "How the server interpreted or ignored arguments.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / examples
      Added value: +{
      +  "description": "Example values when a required argument was missing.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "found",
      -  "not_found",
      -  "no_upcoming",
      -  "invalid_request",
      -  "temporary_error"
      -]New value: +[
      +  "found",
      +  "not_found",
      +  "no_upcoming",
      +  "missing_argument",
      +  "invalid_request",
      +  "temporary_error"
      +]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state that this is a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds the returned field list and source website, but it does not disclose failure behavior, whether one of id/url is required, or other operational details beyond the annotations.

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?

The description is front-loaded and mostly a single efficient sentence listing the event fields. The bilingual '/ Szczegóły jednej imprezy' tail is redundant and the return-field list overlaps with the output schema, but the overall structure is clear.

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?

The output schema covers return values and the annotations cover safety, so the description need not explain those. However, it omits whether at least one of id or url must be supplied and what happens when neither is provided or the event is not found.

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 description coverage is 100%, and the description repeats that lookup can be by id/slug or page URL. It adds the 'or' relationship between the two lookup methods but no syntax or constraints beyond what the schema already provides.

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 clearly states that this retrieves one event on GdzieZabawa.pl by id/slug or page URL and enumerates the returned fields, so the resource is unambiguous. It does not explicitly name or differentiate sibling tools such as search_events, so it falls short of the top score for sibling differentiation.

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 implies that an id or URL is needed, but it gives no explicit when-to-use guidance, no alternatives, and no exclusions. An agent must infer from the schema that the id typically comes from search_events.

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