Skip to main content
Glama

Listing: venue text, amenities and photos

get_listing
Read-onlyIdempotent

What a guest sees at the top of the booking page: the description of the place, its amenities and its photos. Also the booking rules and the seasonal prices. 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_listing"
  }
}

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

A3.7/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent operation. The description adds useful scope beyond that: it returns the guest-facing presentation layer plus booking rules and seasonal prices, and it acts on exactly one venue identified by address and access key.

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?

The description is front-loaded with the visible booking-page content and then adds booking rules and seasonal prices before stating the one-venue scope. It is compact and readable, with only minor redundancy in restating the two required parameters.

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 read-only two-parameter tool with full schema descriptions and no output schema, the description adequately explains what content the listing contains and that it targets a single venue. It is missing explicit sibling differentiation, which is the main remaining gap.

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 coverage is 100%, so the address and access_key parameters are already documented in detail. The description only restates that the tool acts on one venue given its address and access key, adding no extra format, lookup, or constraint information beyond the schema.

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?

The description states a specific read resource and its contents: guest-facing listing text, amenities, photos, booking rules and seasonal prices, scoped to one venue. It is clear what the tool returns, but it does not distinguish itself from sibling get_venue or set_listing by name or explicit boundary.

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 'What a guest sees at the top of the booking page' implies the tool is for inspecting guest-facing listing content, but it gives no explicit when-to-use guidance relative to get_venue or set_listing. Alternatives and exclusions are left implicit.

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