Skip to main content
Glama

Search live merchant status

search_live_status
Read-only

Optional peek at a recent owner answer without asking anything. You usually don't need it — request_live_status already reuses a fresh answer in one call. Returns {found, status, note, verifiedAt, validUntil} or {found:false}. Same scope as request_live_status (stock, wait, seats right now); topic is a bare token like '두바이 쫀득 쿠키'.

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": {
      "placeId": "<placeId>",
      "topic": "<topic>"
    },
    "name": "search_live_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesBare subject token, e.g. '두바이 쫀득 쿠키', '웨이팅', '10명 입장'.
placeIdYesPlace id from a search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior — that it peeks at a cached owner answer without asking anything, and the exact return fields including the {found:false} miss case — which matters since there is no output schema. It stops short of stating freshness/staleness limits or what happens when validUntil has passed, which is the key behavioral risk for a cache-read tool.

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?

Four short sentences, front-loaded with the discouraging 'you usually don't need it' caveat before the return contract. The parenthetical scope reminder and inline example are compact, though the return-field list is dense and could be trimmed given the schema already defines the inputs.

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?

For a two-parameter read tool with no output schema and full annotation coverage, the description supplies the missing pieces: the cache-vs-request distinction, scope, and the return contract. The only material gap is disambiguation against get_live_status and wait_for_live_status, which leaves residual risk of an agent picking the wrong sibling.

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 100%, with both placeId and topic documented in-schema including examples, so the baseline is 3. The description reinforces the 'bare token' nature of topic and repeats an example, but adds no new constraint such as how tokens are matched or what happens on a partial match.

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 uses a specific framing — an optional peek at a recently cached owner answer rather than a new request — and names the return shape, so an agent understands it is a non-triggering read. However, it only differentiates itself from request_live_status and leaves the near-identical siblings get_live_status and wait_for_live_status unaddressed, so full sibling separation is incomplete.

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?

It gives explicit when-not guidance ('You usually don't need it — request_live_status already reuses a fresh answer in one call'), which is the strongest routing signal here. The positive case for using it (checking the cache without creating a request) is only implied by 'optional peek', so the guidance is clear but one-sided.

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.