Skip to main content
Glama

Get venue details

get_venue_details
Read-onlyIdempotent

Full public details of one verified venue: description, capacity, prices, facilities, extras, address and booking page link.

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": {
      "venue_id": "<venue_id>"
    },
    "name": "get_venue_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoResult language: "zh" (default) or "en".
venue_idYesA venue_id from search_venues, such as "venue:my-party-room" or "hotel:my-hotel".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by signalling the scope is 'public' details only and by itemising what the response contains (including a booking page link) in the absence of an output schema.

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 front-loaded sentence that leads with the action and scope, then enumerates return fields. Every clause earns its place with no filler.

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?

With no output schema, the description usefully enumerates what comes back, which is the main gap it needed to fill for a two-parameter detail lookup. Minor omissions remain: no mention of the language parameter's effect on results or behaviour when a venue_id is unknown.

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 venue_id documented as coming from search_venues and the language enum explained, so the schema carries the burden. The description adds no parameter-level meaning, not even that results can be returned in zh or en, so the baseline 3 applies.

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?

States a specific verb+resource (fetch full public details of one verified venue) and enumerates the returned content: description, capacity, prices, facilities, extras, address, booking link. The singular 'one verified venue' implicitly separates it from search_venues, though the separation is not stated explicitly.

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: an agent can infer this is the follow-up to a search when it needs full detail on a single venue. There is no explicit when-to-use, when-not-to-use, or named alternative; the useful hint that venue_id comes from search_venues lives in the schema, not the description.

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