Skip to main content
Glama
xs-mahbub

WPCafe MCP Server

by xs-mahbub

update_seat_plan

Modify an existing seat plan by renaming it or updating its canvas layout data in WPCafe.

Instructions

[WPCafe Pro] Update an existing seat plan (rename or change canvas layout data).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSeat plan ID
nameNoNew name
canvas_dataNoUpdated Fabric.js canvas JSON
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'update' (a mutation) and mentions rename/change, but does not disclose authorization needs, side effects, or limits.

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 a single sentence, front-loaded with the tool's purpose, with no wasted words or repetition.

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?

Despite 100% schema coverage, the description lacks guidance on response behavior, data format details, or implications of updating canvas_data. As a mutation tool with no annotations, it is incomplete.

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%. The description confirms the purpose of name and canvas_data parameters but adds no additional meaning beyond the schema descriptions.

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 clearly states the tool updates an existing seat plan, specifying two specific use cases (rename or change canvas layout data), which distinguishes it from sibling tools like create_seat_plan or delete_seat_plan.

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 description implies usage when an existing seat plan needs modification but provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xs-mahbub/wpcafe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server