Skip to main content
Glama

Event details & how to sign up

get_event
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] Details for one event: whether foreigners can sign up (yes / no / not confirmed, with the basis), step-by-step sign-up guide, official link, a Trip-Pups link, and transport hints.

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
idYesEvent id from search_events
langNoResponse language: en (default) or koen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful disclosure beyond that: the sign-up answer has three possible states (yes / no / not confirmed) and comes with its basis, which tells the agent how much confidence to convey. It does not discuss caching, rate limits, or what happens when an event id is unknown.

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?

It is a single sentence, front-loaded with the core purpose before the content enumeration, and nearly every listed item tells the agent something it would want to know. The bracketed brand/domain prefix is somewhat noisy but establishes the foreigner-festival context the rest of the sentence depends on.

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?

There is no output schema, so the description carries the burden of describing return content, and it does so by enumerating each field an agent would relay to a user. Combined with annotations covering the read-only safety profile and a fully documented two-parameter schema, nothing needed to call this correctly is missing.

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 coverage is 100% for both parameters, and the schema already documents 'id' as coming from search_events and 'lang' as an en/ko enum with an en default. The description adds no further meaning about either parameter, so the 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 states a specific verb (get details) and resource (one event), then enumerates exactly what makes up those details: sign-up eligibility with a yes/no/not-confirmed verdict plus the basis, a step-by-step sign-up guide, official link, Trip-Pups link, and transport hints. That is far more specific than a restatement of the name. It does not, however, distinguish itself from siblings such as get_signup_link or get_walk_guide even though it apparently contains overlapping content.

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: an agent can infer this is the detail-fetch that follows an event listing, and the schema note that 'id' comes from search_events reinforces the chain. But the description itself never says when to pick this over get_signup_link or get_walk_guide, and gives no prerequisites or 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.

Resources