parentsquare-mcp

Overview Schema Source Related Servers Discussions Admin

edit_staff

Update a staff member's name, email, phone, title, or staff ID without changing class assignments or access level. Need user_id from list_staff.

Instructions

Update a staff member's name, email, phone, title, or staff ID. Requires PS_ENABLE_WRITES.

Only provided fields change; everything else — including their class assignments and STAFF/ADMIN access level — is left untouched. Get the user_id from list_staff(school_id). To change which classes they teach, use add_class_staff / remove_class_staff instead. Guardians are rejected: use edit_parent for those.

Args: school_id: School ID user_id: Staff member's user ID (from list_staff) first_name: New first name (optional) last_name: New last name (optional) email: New email (optional) phone: New phone (optional) title: New title shown at the school, e.g. "3rd Grade Teacher" (optional) staff_id: The school's own staff/external ID (optional)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No
`phone`	No
`title`	No
`user_id`	Yes
`staff_id`	No
`last_name`	No
`school_id`	Yes
`first_name`	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

A5/5.0

Behavior5/5

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

No annotations are present, so the description carries the full burden. It discloses the PS_ENABLE_WRITES requirement, states that only provided fields change, explicitly says class assignments and STAFF/ADMIN access level are left untouched, and notes that guardians are rejected. This makes side-effect behavior clear for a mutating operation.

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 front-loaded with a one-sentence purpose, followed by a compact behavioral note and a clean Args block. There is no filler; every sentence provides actionable guidance.

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 mutating tool with two required identifiers and six optional update fields, the description covers prerequisites, side-effect boundaries, alternative routing, and all parameter meanings. An output schema exists, so return-value documentation is unnecessary; nothing essential for correct invocation is missing.

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%, so the manual Args list is essential. It annotates school_id and user_id as identifiers, clarifies staff_id as the school's own external ID, gives an example for title, and marks every optional attribute, adding semantics the schema lacks.

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 first sentence names the exact operation ('Update a staff member's') and enumerates affected fields (name, email, phone, title, staff ID). It also separates itself from sibling tools by naming add_class_staff/remove_class_staff and edit_parent for related actions, making its purpose unambiguous.

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?

It explicitly says to use add_class_staff/remove_class_staff for class changes and edit_parent for guardians, and tells the agent to obtain user_id from list_staff(school_id). This gives clear when-to-use and alternatives guidance with no ambiguity.

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