Skip to main content
Glama

Seoul Events

seoul_events
Read-onlyIdempotent

Seoul cultural events, exhibitions, concerts, festivals, performances, with title, category, district, date, venue, target audience, and fee. Use for "cultural events in Seoul", "what's on in ".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10
    },
    "name": "seoul_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events (default 5; sample key caps at 5, real key up to 1000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so safety is covered. The description adds value by listing the fields returned, which matters because no output schema exists, but it says nothing about data source, refresh cadence, auth requirements, or what an empty result looks like.

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 compact sentences with the resource list front-loaded and trigger phrases at the end. The category enumeration is slightly redundant but no sentence is wasted.

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?

For a simple read-only, single-parameter tool with rich annotations and no output schema, the description covers what the tool returns, which is its main obligation. The gap is the district-filtering implication and the absence of any note on how completeness or pagination of results behaves.

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 100%, so the single `limit` parameter is fully documented in the schema, and the description adds no meaning about it. Worse, the quoted use case 'what's on in <Seoul district>' implies district filtering that has no corresponding parameter, which could lead an agent to expect filtering the tool cannot perform.

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 exact resource (Seoul cultural events) and enumerates the returned fields (title, category, district, date, venue, target audience, fee), which makes it easy to distinguish from siblings like seoul_air_quality or seoul_real_estate. It lacks an explicit verb such as 'list' or 'search', so an agent must infer that it is a query tool, but the scope is unambiguous.

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?

Quoted trigger phrases ('cultural events in Seoul', 'what's on in <Seoul district>') give implied usage context. However, there are no exclusions, no mention of adjacent tools, and no statement of when this tool is a poor fit compared with something like seoul_dataset.

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.