Skip to main content
Glama

PlaceProfile evidence: venue atmosphere, verified (paid)

get_venue

FREE. Full published record for one venue by slug: identity, address, geo, website (the booking path), social links, and, where the venue's owner stated them, hours, telephone and a booking link, category, a plain-English atmosphere description and its atmosphere_basis, and the machine-readable jsonld_url for verification. Numeric atmosphere averages, internal classification tokens, and (for venues measured from their own playlist) genres, territories and dayparts are returned only with include_measurements=true — set it ONLY when the user explicitly asks for figures. Contact email addresses are never included.

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": {
      "slug": "<slug>"
    },
    "name": "get_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
include_measurementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and mostly meets it: it declares the call is FREE, states that some fields are only present 'where the venue's owner stated them', and gives an explicit negative guarantee that contact email addresses are never included. It stops short of describing failure behavior for an unknown slug, truncation, or rate limits.

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?

Opens with the single most decision-relevant token ('FREE.'), then the core purpose, then the conditional flag, then the exclusion. It is one long sentence with a heavy field list, but every clause carries 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.

Completeness4/5

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

With no output schema and no annotations, the description does the work of describing return content in detail, including the conditional field groups and the deliberate omission of emails. What remains thin is error/edge behavior for a bad slug, which matters for a lookup-by-key tool.

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 0%, so the description must supply the meaning, and it does for include_measurements: what it unlocks, which field groups depend on it, and the strict condition for setting it. The required slug parameter gets only the phrase 'by slug' with no format or lookup-failure guidance, which is the one gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full published record for one venue by slug') and then enumerates exactly which fields come back: identity, address, geo, website, social links, hours, telephone, booking link, category, atmosphere, atmosphere_basis, jsonld_url. That field inventory lets an agent tell it apart from a playlist-oriented sibling like get_venue_tracks without opening a schema.

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?

Gives a firm conditional for the optional flag: set include_measurements ONLY when the user explicitly asks for figures, and names what that flag gates (numeric averages, internal tokens, genres/territories/dayparts). It does not name sibling tools or say when to reach for verify_venue or find_venues instead, so tool-level routing guidance is absent.

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