Paxaver MCP Server

Official

by Smartoire

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Create School Event (Admin)

create_school_event

Idempotent

Create a school event with date, time, location, and optional ticketing (price, capacity) for the active school. Requires event coordinator access.

Instructions

ADMIN: Creates a school event, optionally ticketed, at the active school. To change an existing event use update_school_event; to register a parent for an event use register_for_event. Requires pac_cordinator or event_cordinator role. WRITE - only create on explicit user request.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Event name shown to parents
`ends_at`	No	End time (e.g. 20:00)
`location`	No	Event location (e.g. Gymnasium)
`starts_at`	No	Start time (e.g. 18:30)
`event_date`	Yes	Event date, YYYY-MM-DD
`description`	No	Optional event description
`school_slug`	No	School slug (defaults to active school)
`max_capacity`	No	Maximum attendees/tickets; omit for unlimited
`ticket_price_cents`	No	Ticket price in cents (0 = free)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Event ID
`name`	No	Event name
`status`	No	Event status (e.g. active)
`eventDate`	No	Event date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.5.1Sep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the write nature (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds value by requiring a coordinator role and mandating that creation happen only on explicit user request, which are important behavioral guardrails not present in annotations. It does not over-explain side effects, but for a create operation this is sufficient.

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?

Three sentences with no filler: role, action, scope, sibling routing, and explicit-request guardrail are all front-loaded and actionable. Every sentence earns its place.

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

Completeness5/5

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

For a 9-parameter create tool with a 100%-documented input schema and an output schema, the description covers the remaining non-schema essentials: auth requirements, sibling-tool disambiguation, and invocation policy. Nothing critical is missing.

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 the schema already documents all 9 parameters. The description adds useful context that ticketing is optional and that the event is created at the active school, tying to ticket_price_cents/max_capacity and school_slug, but it does not substantially deepen parameter-level meaning beyond that baseline.

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?

States a specific verb ('Creates') and resource ('school event'), and clarifies scope ('at the active school') and optional ticketing. It also names the two sibling tools that handle modifications and registrations, so an agent can distinguish this from update_school_event and register_for_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit role prerequisites, a WRITE / explicit-user-request condition, and direct routing to sibling tools for change (update_school_event) and registration (register_for_event). This leaves little ambiguity about when to invoke this tool versus alternatives.

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