Skip to main content
Glama

Put booking on a website

get_embed_code
Read-onlyIdempotent

Copy-paste code to show this venue’s timetable, packs, services, tables or stays on any website (WordPress, Wix, Squarespace, Webflow, plain HTML), plus a "Book online" button and the booking page link. 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_embed_code"
  }
}

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.8/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 closed-world, so safety is covered. The description adds genuine context beyond them: it operates on exactly one venue, is scoped by address plus access key, and returns code plus a 'Book online' button and the booking page link — a useful preview of payload since there is no output schema.

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 sentences, front-loaded with the action ('Copy-paste code to show this venue's timetable...') followed by the scope constraint. The platform enumeration is slightly listy but earns its place by signaling where the output is meant to be pasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a two-parameter read tool with full schema coverage, complete annotations, and no output schema, the description covers what it produces (embed snippet, button, booking link), the scope (one venue), and the intent (publishing on a site). An agent has everything needed to select and call it correctly.

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%, with both properties documented, so the schema carries the semantics. The phrase 'given its address and access key' only restates that both are needed, adding no format, casing, or lookup guidance beyond the schema's 'name in name.bookare.app' note.

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?

States a specific verb-and-resource pair: retrieve copy-paste embed code for a venue's timetable, packs, services, tables or stays. The enumeration of embeddable content types and the mention of the button and booking link make the output concrete. It stops short of naming a sibling it differs from, so 4 rather than 5.

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 framing 'Put booking on a website' and the platform list (WordPress, Wix, Squarespace, Webflow, plain HTML) imply when to reach for it. There is no explicit when-not guidance and no differentiation from adjacent link/setup tools such as get_claim_link or get_dns_instructions, leaving the agent to infer the boundary.

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