seatcanvas

Estimate venue seating capacity

seatcanvas_estimate_capacity

Read-only

Estimates how many guests a venue of the given width and height can seat at a chosen table type, and returns a link to a prefilled SeatCanvas plan. Read-only; deterministic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Language for the prefilled plan: 'en' (default) or 'es'.	en
`venue_h`	Yes	Venue height/depth in the chosen unit_system (meters or feet).
`venue_w`	Yes	Venue width in the chosen unit_system (meters or feet).
`event_type`	No	Event type: 'wedding' (adds a head table), 'quinceanera', 'corporate', or 'other'. Default 'other'.	other
`table_type`	No	Table shape + seats: 'round-8', 'round-10', 'rect-8', or 'rect-10'. Default 'round-8'.	round-8
`unit_system`	Yes	Unit for venue dimensions: 'metric' (meters) or 'imperial' (feet).

Output Schema

TableJSON Schema

Name	Required	Description
`planner_url`	Yes	Prefilled SeatCanvas planner URL.
`raw_capacity`	Yes	Honest estimated seating capacity for the venue (may be 0).
`preview_guest_count`	Yes	Guest count used to seed the preview canvas (always >= 1).

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool as read-only and non-destructive. The description adds 'deterministic' and clarifies it returns a link. This is sufficient but could further describe what happens on invalid inputs (e.g., negative dimensions).

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 with no redundancy. The first sentence concisely captures the core functionality; the second adds safety context. Every word earns its place.

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?

Given the presence of an output schema (not shown) and comprehensive parameter descriptions, the description is nearly complete. It covers inputs, output (link), and safety. Minor gap: no mention of error behavior or limits on dimensions.

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 individual parameter descriptions. The tool description summarizes the role of venue dimensions and table type but does not add new semantic context beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific verb ('estimates') and resource ('seating capacity'), includes key inputs (width, height, table type), and distinguishes itself from siblings (seatcanvas_create_plan, seatcanvas_get_pricing) by focusing on estimation rather than creation or pricing.

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 purpose is clear but the description does not explicitly state when to use this tool versus alternatives like seatcanvas_create_plan (for actual plan creation) or seatcanvas_get_pricing (for cost). Users must infer from sibling names; an explicit guidance sentence would help.

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

All seatcanvas tools Inspect

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

Need Help?