Skip to main content
Glama

seatcanvas

by app.seatcanvas

Create a prefilled seating plan

seatcanvas_create_plan
Read-only

Returns a link to a SeatCanvas plan prefilled with a table layout for the given guest count and event type (optional venue dimensions). Opening the link seeds the canvas; nothing is saved until the user signs in. Read-only; deterministic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoLanguage for the prefilled plan: 'en' (default) or 'es'.en
venue_hNoOptional venue height/depth in the chosen unit_system; omit to auto-size.
venue_wNoOptional venue width in the chosen unit_system; omit to auto-size a venue to fit the guests.
event_typeYesEvent type: 'wedding' (adds a head table), 'quinceanera', 'corporate', or 'other'.
table_typeNoTable shape + seats: 'round-8', 'round-10', 'rect-8', or 'rect-10'. Default 'round-8'.round-8
guest_countYesNumber of guests to seat (positive integer).
unit_systemYesUnit for venue dimensions: 'metric' (meters) or 'imperial' (feet).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
guest_countYesGuest count the plan was built for.
planner_urlYesPrefilled SeatCanvas planner URL.
table_countYesNumber of tables in the seeded plan (includes the head table for weddings).

TDQS

A4.2/5.0
Behavior4/5

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

Adds useful behavioral details beyond annotations: 'seeds the canvas', 'nothing saved until sign-in', 'read-only; deterministic'. Annotations already cover read-only and non-destructive nature.

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, no fluff, front-loaded with key action and constraints. Every sentence adds value.

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?

Adequately describes the tool's purpose and side effects; output schema exists so return value explanation is unnecessary. Could briefly mention the link nature, but sufficient.

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 coverage is 100% with descriptions for all parameters. The description does not add new meaning or clarify usage beyond what schema provides, so baseline score applies.

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?

Clearly states it returns a link to a prefilled seating plan for given guest count and event type, distinguishing itself from siblings that estimate capacity or get pricing.

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?

Provides context: the link seeds a canvas and nothing is saved until sign-in, implying use for preview. No explicit exclusions or alternative tool references beyond sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All seatcanvas toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct function: plan creation, capacity estimation, and pricing. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent seatcanvas_verb_noun pattern (create_plan, estimate_capacity, get_pricing) with clear verbs and nouns.

Tool Count5/5

Three tools are well-scoped for the server's purpose: creating plans, estimating capacity, and retrieving pricing. No tools are extraneous.

Completeness4/5

The set covers the main domain actions: creating plans, estimating capacity, and getting pricing. Missing possible plan modification tools, but the service is described as read-only and deterministic, so this is acceptable.

Resources