Skip to main content
Glama

Services, staff or tables, and hours

get_agenda_setup
Read-onlyIdempotent

What the venue offers by appointment (services with duration and price, staff) or, for restaurants, its tables; and the opening hours. 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_agenda_setup"
  }
}

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description earns credit by disclosing what the payload contains (services with duration and price, staff, tables, opening hours and hours of operation) — valuable because there is no output schema — and by stating the single-venue scope. It does not cover error behavior for an unknown address or how large venues are paginated.

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?

A single dense sentence with no filler; every clause carries content (services/prices/staff, tables, hours, single-venue scope). The semicolon-heavy construction and trailing scope clause make it slightly harder to scan than a front-loaded verb-first sentence, but nothing is wasted.

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 two-required-parameter read tool with full schema coverage and no output schema, the description adequately covers what the call returns and what it operates on. Gaps are minor: no shape of the response envelope, no indication of what happens when the address is unknown or the key is wrong.

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 both parameters (address, access_key) are already documented in the schema. The description reinforces that the tool acts on exactly one venue identified by those two values, which implies no cross-venue queries, but adds no syntax or format detail beyond the schema. 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?

The description names the concrete resources returned (services with duration and price, staff, restaurant tables, opening hours) and scopes it to a single venue, which clearly separates it from mutating siblings like add_service, add_table and set_opening_hours. It never states an explicit verb such as 'retrieve' or 'read' and never names a sibling, so the read intent must be inferred from context and annotations.

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 get_venue, get_listing or get_timetable, and no prerequisites or exclusions beyond the address/access-key requirement already in the schema. The only guidance-like content is the conditional 'for restaurants, its tables', which explains content variation by venue type rather than when to select this tool.

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