parentsquare-mcp

Overview Schema Source Related Servers Discussions Admin

add_staff

Add a teacher or staff member to a school and assign them to classes right away, even before they register, by creating the class assignment directly.

Instructions

Add a teacher or other staff member to a school. Requires PS_ENABLE_WRITES.

ParentSquare emails the new account an address-verification/registration invite. Passing section_ids assigns them to those classes right away (as class_role, default TEACHER) — verified live, because ParentSquare's own "invited classes" field does not create the assignment until the person registers, so this tool makes the assignment itself.

Args: school_id: School ID first_name: Staff member's first name last_name: Staff member's last name email: Email address (optional but needed for them to register) phone: Phone number (optional) title: Title shown at the school, e.g. "3rd Grade Teacher" (optional) staff_id: The school's own staff/external ID (optional) is_admin: True to grant school Admin rather than Staff access section_ids: Class/section IDs to assign them to (from list_classes) class_role: Role for those classes — TEACHER (default) or ASSISTANT

Input Schema

TableJSON Schema

Name	Required	Default
`email`	No
`phone`	No
`title`	No
`is_admin`	No
`staff_id`	No
`last_name`	Yes
`school_id`	Yes
`class_role`	No	TEACHER
`first_name`	Yes
`section_ids`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and succeeds: it discloses that ParentSquare emails a registration invite, that section_ids create direct assignments because ParentSquare's own 'invited classes' field delays assignment until registration, and that is_admin grants Admin rather than Staff access.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The structure is effective: a one-sentence purpose, a compact behavioral note about the registration invite and section assignment, and a skimmable Args list. It is slightly wordy in the ParentSquare explanation, but that detail justifies 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 10-parameter mutation tool with no annotations and an output schema, the description is complete: it covers required permissions, side effects, parameter semantics, and the non-obvious class-assignment behavior. Return values are appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully by explaining every parameter, including optionality, defaults, and provenance. Examples include email being 'optional but needed for them to register,' section_ids coming 'from list_classes,' and class_role being 'TEACHER (default) or ASSISTANT.'

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 opens with a specific verb and resource: 'Add a teacher or other staff member to a school.' This clearly distinguishes the operation from sibling tools like add_student and add_parent, and the mention of class_role and is_admin further sharpens the scope.

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?

It provides clear context for when to use the tool—adding staff and optionally assigning them to classes immediately—and states the prerequisite PS_ENABLE_WRITES. It does not explicitly name alternatives such as add_class_staff or edit_staff, so exclusion guidance is left to inference.

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