Skip to main content
Glama

대전한콕 Daejeon Hankok

events_and_deals

Read-onlyIdempotent

대전 축제·공연·전시 일정(kind=events) 또는 착한가격업소 — 만원 점심·저렴한 미용실(kind=deals).

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": {
      "kind": "<kind>"
    },
    "name": "events_and_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description adds domain context (Daejeon-only, curated budget categories) but says nothing about result volume, ordering, pagination, or freshness of schedules. Adding the geographic scope is useful; the rest is absent.

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 compact sentence with both modes front-loaded and no filler. The parenthetical enum tags make the branch structure scannable. Slight density cost from cramming two domains plus examples into one line, but nothing is wasted.

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?

This is a one-parameter, enum-only read tool with full annotation coverage and no output schema. The description defines both modes and the domain, which is everything an agent needs to call it correctly. No meaningful gap remains for a tool of this complexity.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does: it explicitly defines what kind=events returns (festival/performance/exhibition schedules) and what kind=deals returns (affordable restaurants and hair salons). The enum values are enumerated in the schema, but the semantic payload of each is only explained here.

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 specific resources: Daejeon festival/performance/exhibition schedules and budget-friendly businesses (cheap lunch, low-cost hair salons). An agent can immediately tell this is a local listings tool for two distinct content domains. It stops short of a 5 because it never contrasts itself with siblings like search_places or get_place.

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?

The inline kind=events / kind=deals mapping implicitly tells the agent which mode to select for which need, which is genuine routing guidance. However, there is no explicit statement of when to prefer this tool over search_places, get_place, or search_stylists, and no exclusions or prerequisites are given.

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