Skip to main content
Glama

Little Works

create_booking

Stage a booking (guest or signed-in). Requires apiKey when server key is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
guestNameNo
serviceIdNo
slotStartNo
guestEmailNo
scheduleSlugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry behavioral disclosure. It notes the API key condition and that the booking is staged, but does not explain whether a slot is held, how long it lasts, whether it is a write operation, or what happens on failure.

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?

The description is two short sentences, front-loaded with the main action and the auth condition. There is no unnecessary wording.

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

Completeness2/5

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

Given six parameters, no annotations, no output schema, and very low schema coverage, the definition is far too sparse. It leaves the core booking behavior and most parameter semantics unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, and the description only mentions apiKey, which is already documented in the schema. It does not clarify guestName, serviceId, slotStart, guestEmail, or scheduleSlug or which fields are required in practice.

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 action and resource: it stages a booking and covers guest or signed-in modes. It does not explicitly distinguish this from create_checkout or explain what staging means, so sibling differentiation is limited.

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?

Provides some context for guest vs signed-in use and the conditional apiKey requirement, but it gives no explicit when/when-not guidance or alternative such as checking slots or using checkout.

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