parentsquare-mcp

Overview Schema Source Related Servers Discussions Admin

add_parent

Create a guardian and link them to a student in the ParentSquare roster. Provide school ID, student ID, and guardian first/last name to add a parent contact.

Instructions

Create a guardian/parent and link them to a student. Requires PS_ENABLE_WRITES.

A parent is always created attached to at least one student. The new user id is not returned — call list_students or the parent roster afterward.

Args: school_id: School ID student_id: Student ID to attach the guardian to (from list_students) first_name: Guardian first name last_name: Guardian last name email: Guardian email (optional) phone: Guardian phone (optional)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No
`phone`	No
`last_name`	Yes
`school_id`	Yes
`first_name`	Yes
`student_id`	Yes

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

A3.7/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a required permission (PS_ENABLE_WRITES), the invariant that a parent is always attached to at least one student, and the notable behavior that the new user id is not returned. These are important and beyond what the schema conveys.

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 description is efficiently structured: a short introductory paragraph followed by an Args block. The key points (requirement and no return id) are front-loaded, and the parameter list is easy to scan. No wasted sentences.

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

Completeness4/5

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

For a create tool with 6 parameters and an output schema, the description covers the essential prerequisites, the attachment requirement, and the crucial fact that the new id is not returned. It omits error behavior and field formats, but these are not critical for basic invocation. Given the output schema exists, it doesn't need to explain return values beyond the id note.

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 0%, so the description must add meaning. It provides a brief line for each parameter (e.g., 'student_id: Student ID to attach the guardian to (from list_students)') which adds context beyond titles, but the descriptions are minimal and don't explain formats, constraints, or relationships beyond the basic mapping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Create') and resource ('guardian/parent') and specifies the linking to a student. It is unambiguous about what the tool does. However, it does not explicitly differentiate from sibling tools like link_guardian_to_student, so it falls short of a 5.

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 when to use it (to create a new parent) but does not mention alternatives or explicitly state when not to use it. It gives a prerequisite (PS_ENABLE_WRITES) but lacks clear routing among the many parent-related siblings.

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