Skip to main content
Glama

Create a venue for an owner

create_venue

Creates a draft venue for a business owner. Returns the booking page address, an access key for that venue, the venue’s own MCP address, and a claim link. The venue opens to customers only after the owner claims it with a code sent to their email; unclaimed drafts are deleted after 14 days.

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": {
      "business_type": "<business_type>",
      "name": "<name>",
      "owner_name": "<owner_name>",
      "owner_email": "<owner_email>",
      "country": "<country>"
    },
    "name": "create_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBusiness name as customers know it.
addressNoOptional wanted address, the "name" in name.bookare.app. Default: made from the business name.
countryYesTwo-letter ISO code, e.g. GR. Sets the prices of the plans.
languageNoMain language of the venue’s pages. Default el for GR and CY, else en.
agent_nameNoWho is setting it up, e.g. "Claude for Acme Web Studio". Shown to the owner when claiming.
owner_nameYes
owner_emailYesThe owner’s real email: they confirm the claim with a code sent there.
business_typeYesKind of business: gym, salon, restaurant, hotel, camping, rental or stay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / business_type / description
      Previous value: -"From list_business_types, e.g. gym, salon, restaurant, hotel, camping, rental, stay."New value: +"Kind of business: gym, salon, restaurant, hotel, camping, rental or stay."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the return payload (booking page address, access key, venue MCP address, claim link), the claim-by-emailed-code gate before the venue is customer-visible, and a 14-day deletion window for unclaimed drafts. That lifecycle and expiry context is exactly the kind of behavior annotations can't convey. It stops short of addressing duplicate/retry behavior flagged by idempotentHint=false or any auth prerequisites.

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?

Two sentences, front-loaded with the action, then the return values and the lifecycle caveat. Every clause carries information an agent needs; nothing is repeated from the title or schema.

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 enumerates what comes back, and it discloses the draft/expiry model for a non-destructive but stateful mutation. What remains missing is small: no note on repeat-call behavior or what happens if the email is invalid, but the agent has enough to invoke 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 88%, so the schema already carries parameter meaning (country sets plan prices, language defaults, owner_email is where the claim code goes). The description adds no parameter-level detail of its own, so 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?

States a specific verb and resource plus a key qualifier: it creates a *draft* venue for a business owner. An agent can immediately tell this is the creation entry point versus the read-only siblings (list_venue_tools, get_plans, check_address). It doesn't explicitly name a sibling to contrast with, which keeps it from a 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?

Usage is implied by the name and purpose (set up a new venue on behalf of an owner), but there is no explicit when-to-use/when-not guidance. Given siblings like check_address and list_business_types, the description could have said to resolve the address or pick a business type first; that prerequisite routing is absent.

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