parentsquare-mcp

Overview Schema Source Related Servers Discussions Admin

edit_class

Update class details by renaming it or changing its room code or grade assignments. Provide the class and school IDs, then specify the fields to modify.

Instructions

Rename a class or change its room code / grades. Requires PS_ENABLE_WRITES.

Only provided fields change — current values are read back from the class first and resent, because the underlying endpoint replaces what it is given. Staff are not affected; use add_class_staff / remove_class_staff for those.

Args: section_id: Class/section ID (from list_classes) school_id: School ID the class belongs to name: New class name (optional) room: New room code / external ID, e.g. "Room 5" (optional) grade_ids: New list of grade IDs (optional; replaces the current grades)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section_id": "<section_id>",
      "school_id": "<school_id>"
    },
    "name": "edit_class"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`room`	No
`grade_ids`	No
`school_id`	Yes
`section_id`	Yes

Output 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?

With no annotations, the description carries the full behavioral burden, and it delivers: it discloses the read-modify-write mechanism, states that only supplied fields are changed, and warns that grade_ids replaces the current grades. This gives the agent accurate expectations about side effects.

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?

Each line carries distinct information: purpose, permission, behavioral mechanism, staff exclusion, then a clean Args block. There is no filler, and the most decision-relevant details are front-loaded.

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 5-parameter write tool with zero annotation coverage, the description covers prerequisites, update semantics, parameter semantics, and the alternative for staff. The presence of an output schema means the lack of return-value documentation is not a gap.

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 description must explain every parameter, and it does: section_id is sourced from list_classes, name/room are marked optional with a format example, and grade_ids is explicitly 'new list ... replaces the current grades.' This adds substantial meaning beyond the bare types and null defaults.

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 opening sentence states a precise action and resource: 'Rename a class or change its room code / grades.' It enumerates exactly which attributes are editable, so an agent can immediately distinguish edit_class from sibling mutators like set_class_visibility or add_class_staff.

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 gives an explicit precondition ('Requires PS_ENABLE_WRITES') and a when-not-to-use rule: 'Staff are not affected; use add_class_staff / remove_class_staff for those.' This is a clear decision rule that prevents the most likely misuse, without making the agent infer from the sibling list.

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