Skip to main content
Glama

DealLabs

Find active pop-ups

find_active_popups
Read-only

Pop-ups running on a day. Returns an empty list with reason_code no_v1_records until the city publishes pop-up records in data-standard v1.

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

Input Schema

NameRequiredDescriptionDefault
atNo
areaNo
cityYesCity key, e.g. "seoul".
dateNoDefault: today in the city's own time.
stationNo
categoryNo
walk_maxNo
open_untilNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely non-obvious behavior: the call may return an empty list with reason_code no_v1_records until the city publishes v1 records. That prevents the agent from misreading an empty result as 'no pop-ups today'. It does not cover pagination, limits, or what a successful payload looks like beyond that edge case.

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?

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the empty-result caveat. Nothing is repeated from the title or schema.

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 an eight-parameter tool with no output schema, the description does well to explain the empty-result contract, but it leaves most filter parameters undefined and gives no hint about what a populated response contains. An agent could call it with only city/date, but the richer filtering capability would be undiscoverable.

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 description coverage is only 25% — just city and date are documented — yet the description explains only 'on a day' and the city publication caveat. The six remaining parameters (at, area, station, category, walk_max, open_until) receive no meaning from the description, leaving the agent guessing at filters like walk_max and open_until.

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 a specific verb and resource — pop-ups running on a given day — so the agent knows exactly what is returned. It does not reference any sibling tool, but the sibling names (get_station_exit, plan_local_route, search_verified_places) are functionally distinct enough that confusion is unlikely.

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?

Usage is only implied by 'Pop-ups running on a day'; there is no explicit when-to-use, when-not-to-use, or named alternative. The data-standard caveat does hint at a condition under which results are useless, which is useful context, but the agent still has to infer that this tool replaces a general place search for pop-up queries.

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