Skip to main content
Glama

Collect results into a My Korea link

make_my_korea_link
Read-onlyIdempotent

한국 여행 안내·관광 통계 (Korea Basics): Build one link from ids returned by the other tools (the saveToMyKorea field of their results: rules and guides, places, events, tool cards). Use it at the end of a trip-planning conversation, or whenever the user wants to keep what came up. Opening it shows the collection on Korea Basics, where the user can tap to save items to My Korea and manage them before the trip (changes to saved rules, own schedule, calendar). Nothing is saved until the user does it on the site. Takes up to 10 items (rules, guides, collections, events, tool cards) and 90 places; rules needed before departure are kept first.

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

Input Schema

NameRequiredDescriptionDefault
toolsNoTool card ids, e.g. ["plug-card", "tmoney-card"].
eventsNoEvent ids from get_korea_dates.
placesNoPlace ids or names.
topicsNoRule, guide and collection ids, e.g. ["k-eta", "customs-allowance", "royal-palaces"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds the crucial behavior that no state is written server-side — 'Nothing is saved until the user does it on the site.' It also discloses capacity limits (10 items, 90 places) and ordering ('rules needed before departure are kept first'), which annotations cannot convey.

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-loaded with the core action and input source, then the lifecycle and limits. Slight redundancy in re-listing item types ('rules and guides, places, events, tool cards' appears twice) and the parenthetical brand label adds little, but nothing is seriously 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?

With no output schema, the description still explains the return: a link that opens the collection on Korea Basics where the user saves and manages items. For a zero-required-parameter aggregator tool, that covers what an agent needs to construct and present the result.

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 coverage is 100% so the baseline is 3, but the description adds real meaning: which upstream field supplies the ids, what each id class represents (tool cards, events, rules/guides/collections, places or names), and item caps. Minor tension: the stated caps (10 items, 90 places) sit alongside schema maxItems of 100, which could confuse an agent filling arrays.

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 artifact — 'Build one link from ids returned by the other tools' — and pins down the exact input source (the `saveToMyKorea` field of results). That distinguishes it clearly from siblings like find_korea_places or get_korea_topic, which produce ids rather than collect them.

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

Usage Guidelines5/5

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

Explicit when-to-use: 'at the end of a trip-planning conversation, or whenever the user wants to keep what came up.' It also implicitly routes agents here after the other tools by naming the field to pull ids from, so an agent knows both the trigger and the prerequisite.

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