Skip to main content
Glama

Change venue details

update_venue

Changes the venue’s name, legal name, address, phones, contact email, website or opening hours: what customers see at the bottom of every page and in emails. Only the fields you send change; send an empty value to clear one. The venue type, country and booking address cannot be changed here. 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": "update_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or area, e.g. "Zografou".
nameNoVenue name (2-80 characters).
emailNoContact email shown to customers.
phonesNoUp to two phone numbers, the main one first. Numbers without a country code are taken as the venue’s country.
streetNoStreet and number, e.g. "Agias Lavras 5-7".
addressYesThe venue’s address name, the "name" in name.bookare.app.
websiteNoThe venue’s own website, full address like https://example.gr. Used for the “back to site” button.
access_keyYesThe venue’s access key.
legal_nameNoThe business’s legal name, shown on the privacy page as the data controller.
postal_codeNoPostal code, e.g. "157 73".
opening_hoursNoOpening hours, one line per group of days (up to 7 lines), e.g. ["Mon–Wed 09:00–13:00 & 16:00–21:00", "Sat 09:00–14:00"]. Empty list clears them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: it is a patch-style update where unsent fields are preserved and empty values clear a field, which is exactly the kind of detail an agent needs before mutating customer-visible data. It does not describe the response or any validation/failure behavior, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the mutable field list, then patch semantics, then exclusions, then the targeting key. No filler and nothing repeated from the schema or annotations.

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 an 11-parameter mutation tool with no output schema, the description covers scope, partial-update behavior, clearing, and exclusions, which is the bulk of what an agent needs. The remaining gap is return/confirmation behavior and whether invalid values are rejected wholesale or per field, but annotations and the rich schema carry most of the rest.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: the clearing convention applies across all fields (the schema only states this for opening_hours) and the whole field set is framed as customer-facing content. It also implicitly distinguishes the address identifier from street/city/postal_code by calling out that the booking address is not editable here.

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 (Changes) and resource (the venue) and enumerates exactly which fields are mutable: name, legal name, address, phones, email, website, opening hours. It also names the fields that are out of scope (venue type, country, booking address), which lets an agent separate this from create_venue or the add_* siblings 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 clear operating context: partial-update semantics ("Only the fields you send change"), a clearing rule ("send an empty value to clear one"), and explicit exclusions for fields that cannot be changed here. It stops short of naming the sibling tool that would handle venue type, country, or booking address, so the agent knows what not to do but not where to go instead.

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