Skip to main content
Glama
GraditiPro

standshare-mcp

by GraditiPro

workers

Manage worker assignments for concession stands: view event rosters, assign workers, update attendance, check availability, and view attendance history.

Instructions

Manage worker assignments — view event rosters, assign workers to events/stands, update attendance, check availability, and view attendance history. Workers are family members who work concession stands at events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
dateToNoEnd date for history (ISO 8601)
userIdNoUser ID
eventIdNoEvent ID (required for event_roster, assign, update_assignment, availability)
standIdNoStand ID to assign worker to
dateFromNoStart date for history (ISO 8601)
familyIdNoFamily ID (required for assign)
workerNameNoWorker name (for assign)
assignmentIdNoAssignment ID (required for update_assignment)
rankByHistoryNoRank available workers by attendance history
attendanceStatusNoAttendance status
registrationStatusNoRegistration status
Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral traits such as permissions, destructive actions, or side effects. It only lists action types without context.

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 concise sentences that front-load the purpose and provide essential context without excess.

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

Completeness3/5

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

With 12 parameters and no output schema, the description outlines main actions but does not clarify parameter relationships or action-specific requirements, leaving gaps.

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 100%, so baseline is 3. The description adds no extra parameter meaning beyond the schema.

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 it manages worker assignments and lists specific actions (event rosters, assign, etc.), distinguishing it from siblings like events or families.

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 for worker tasks but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or when-not advice.

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/GraditiPro/standshare-mcp'

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