Skip to main content
Glama

Get listing

get_listing
Read-onlyIdempotent

One listing by id (format ///, as returned by search_places or get_town), with all published facts.

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": {
      "id": "<id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id, e.g. "nagano/hakuba/see/hakuba-folk-history-museum"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact — only published listings are surfaced ('all published facts') — but says nothing about what happens when the id resolves to an unpublished or nonexistent listing.

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 sentence with zero filler; the identifier format and the source of that format are both front-loaded in the position an agent will read first.

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 one-parameter read tool with rich annotations and no output schema, the description supplies what is needed: what is fetched, in what key format, and from where the key originates. Only the unpublished/not-found behavior is left implicit, which is a minor gap given the annotation coverage.

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% and the schema already carries an example id, so baseline is 3. The description goes further by spelling out the segmented structure (<prefecture>/<town>/<section>/<slug>) and, importantly, where such an id comes from, which meaningfully reduces malformed-id calls.

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?

Names the resource ('One listing'), the lookup key ('by id'), and the return scope ('all published facts'), which is enough to distinguish it from search_places and list_towns. The verb is elided into a noun phrase rather than stated outright, so it falls just short of a fully explicit verb+resource statement.

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?

The phrase 'as returned by search_places or get_town' implicitly tells the agent to obtain an id from those tools first, which is useful workflow routing. However, it never states when to prefer this over a search or what to do when the id is unknown, so the guidance is suggested rather than explicit.

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