Skip to main content
Glama

LocalSpot Trip

sights

Sights in a Korean city (optionally one neighbourhood): best time of day, typical visit minutes, closing day, a practical tip.

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": {
      "city": "<city>"
    },
    "name": "sights"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
cityYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral burden. It does disclose the shape of each returned sight (timing, duration, closing day, tip), which is genuinely useful, but it says nothing about whether this is a read-only listing (implicit but unstated), what happens for an unknown city or area, or how many results appear by default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the scope and then lists the returned attributes. Nothing is repeated and no filler is present; every clause conveys new information.

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 three-parameter read tool with no output schema, the description covers the return fields well and clarifies the optional area parameter. It is still missing the meaning of limit and any guidance on what the agent should do with the results or how to handle an empty result set.

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 description coverage is 0%, so the description must compensate. It does clarify two things the schema does not: 'city' means a Korean city and 'area' means a single neighbourhood and is optional. However, 'limit' (1-15) is never explained — whether it caps the number of sights returned — and the expected format of city/area names is unstated.

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 resource (sights in a Korean city) and enumerates what each result carries: best time of day, typical visit minutes, closing day, and a practical tip. This is specific enough to distinguish it from planning tools like trip_plan or place_info, though it never explicitly contrasts itself with find_places or open_nearby.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no statement of what the agent should do with the results, no mention of when to prefer find_places or place_info instead, and no prerequisites (e.g., that the city must already be a known Korean city). Usage is only inferable from the noun phrase.

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