Skip to main content
Glama

Stop-by-stop guide for the Dobong walk

get_walk_guide
Read-onlyIdempotent

[Trip-Pups(트립펍스) — 외국인 축제 찾기·신청] The stop-by-stop guide for the Trip-Pups Dobong Hangeul history walk (event id tp-weekly-dobong-walk-1114): how to get there, what each stop is with sources, Korean phrases, and a line for a taxi driver. Use it when the traveler asks about this walk, before or during it. Answer only from what it returns, in the traveler's language. Other events have no guide here.

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_walk_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idNoLeave empty for the Dobong walk. Only tp-weekly-dobong-walk-1114 has a guide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the content is grounded/sourced, must be paraphrased into the traveler's language, and answers must come only from the response. However it says nothing about size, caching, or freshness of the guide data.

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?

Front-loads the vendor tag and the resource, then packs the trigger and constraints into a tight block with no filler. The bracketed Korean/English brand header and the long parenthetical event id make the opening line denser than ideal, but nothing is padding.

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?

No output schema exists, and the description compensates by listing what the guide contains (arrival directions, stops with sources, phrases, taxi line), which is what an agent needs to decide to call it. The only gap is lack of any statement about how a non-Dobong event_id is handled.

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% and the single optional parameter already documents 'Leave empty for the Dobong walk. Only tp-weekly-dobong-walk-1114 has a guide.' The description restates the same constraint rather than adding new meaning such as accepted formats or the failure behavior for a non-Dobong id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (stop-by-stop guide for the Dobong Hangeul history walk) and enumerates the payload: directions, per-stop explanations with sources, Korean phrases, and a taxi-driver line. The closing note 'Other events have no guide here' separates it from get_event/search_events without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger ('when the traveler asks about this walk, before or during it') plus a scope exclusion for all other events and an answering constraint (respond only from the returned content, in the traveler's language). It doesn't name which sibling to use for non-Dobong events, so routing for the excluded case is left implicit.

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