Skip to main content
Glama

Venue overview

get_venue
Read-onlyIdempotent

Name, type, contact details, booking rules, payment methods and today’s numbers for the connected venue. Acts on one venue, given its address and access key.

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

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful facts beyond that: it is scoped to a single connected venue, and it returns 'today's numbers', signalling volatile, date-sensitive values. It does not say anything about auth failure modes or whether the access key is validated per call.

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 compact sentences, with the payload contents front-loaded so the reader learns the return shape first. The second sentence largely duplicates information already present in the required parameters, which is the only real waste.

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 correctly compensates by enumerating the return fields, and annotations carry the safety profile for a read-only tool. The weak spot is the vague 'today's numbers', which an agent cannot resolve without calling, but overall the definition supports correct invocation.

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%, so the schema already explains both address and access_key, and the description only restates that the call is given those two values. Baseline 3 applies; nothing new such as key sourcing or address format is contributed.

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?

Enumerates the specific resource contents returned: name, type, contact details, booking rules, payment methods and today's figures for the connected venue. That is far more than a restatement of 'Venue overview' and lets an agent predict the payload. It does not explicitly distinguish itself from sibling getters such as get_listing or get_plans, so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus update_venue, get_listing, get_plans, or any other sibling. The only usage-like information is the scoping note that it acts on one venue identified by address and access key, which is really parameter semantics rather than routing guidance.

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