Skip to main content
Glama

Get venue

get_venue
Read-onlyIdempotent

Everything known about one Sydney venue: its menus and dishes with allergen status per dish, venue-wide allergen notes (dedicated fryer, shared prep), how many dishes are free of each allergen, diner ratings for coeliac and allergy friendliness, opening state, address, booking and map links, and the pages the menus were read from with dates. Use the id or slug returned by search_dishes or list_allergen_free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoVenue id from a search result.
slugNoVenue slug from a search result, e.g. 'pinocchio-cremorne', or its page URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds useful provenance context ("the pages the menus were read from with dates") and states that allergen data includes venue-wide prep notes, but it says nothing about behavior on a missing/ambiguous venue or how complete or stale the allergen data may be. That is a modest add beyond the annotations.

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?

Two sentences, front-loaded with the resource, then the usage rule. The long enumerated clause is dense but each item (allergen status per dish, venue-wide notes, free-of counts, diner ratings, opening state, provenance) carries distinct information an agent needs to decide whether to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-value burden, and it does so thoroughly: it enumerates every field family returned including provenance and allergen aggregation. Combined with the annotation-derived safety profile, nothing an agent needs in order to select and call this tool is missing.

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 description coverage is 100%, so the schema itself defines both `id` and `slug`, giving a baseline of 3. The description earns an extra point by telling the agent where those values come from (search_dishes or list_allergen_free), which is not in the schema, and it also conveys the slug format implicitly. It does not state whether at least one of the two optional parameters is required.

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?

"Everything known about one Sydney venue" is a specific verb-plus-resource statement, and the enumeration of menus, dishes, allergen counts, ratings, opening state, address and booking links makes the scope of the record unambiguous. It distinguishes itself from the search/list siblings by naming them as the source of ids, though it doesn't contrast with `compare`.

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?

The second sentence gives a concrete entry condition: call this with an id or slug returned by `search_dishes` or `list_allergen_free`. That is clear usage context, but there is no guidance on which identifier to prefer when both are known, nor any when-not-to-use case.

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