Skip to main content
Glama

unassign_person

Destructive

Removes ONE assignment: the link between a person and a block, with its role and its ownership share on that block. The person stays in the project and keeps every other assignment (delete_person removes the person altogether). Idempotent: if that person is not assigned to that block, the call still answers success and changes nothing — it does not prove the assignment existed. The current assignments of a block are listed by get_cell_details; a removed assignment is re-created with assign_person (the previous share is not kept).

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": {
      "personId": "<personId>",
      "cellId": "<cellId>"
    },
    "name": "unassign_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellIdYesID of the block they are removed from
personIdYesID of the person whose assignment is removed
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cellId / description
      Added value: +"ID of the block they are removed from"
    • addedInput schema / properties / personId / description
      Added value: +"ID of the person whose assignment is removed"
  2. Changed1 schema field changed
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark this as destructive and not read-only, and the description adds substantial behavioral context beyond them: the person stays in the project, all other assignments are kept, the call is idempotent but does not prove the assignment existed, and re-creating with assign_person does not preserve the previous share. These are exactly the side-effect details an agent needs for a destructive mutation.

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 dense but front-loaded: it defines the operation and its scope first, then idempotency, then lookup and re-creation alternatives. Every sentence carries operational value for this destructive mutation, with no wasted repetition.

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 destructive assignment-removal tool with no output schema, the description covers scope, side effects, idempotency, listing, and re-creation behavior. The annotations cover the safety profile, and the schema covers parameters, leaving no major gap an agent would need filled before invoking it.

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 all three parameters, including expectedProjectId and its refusal behavior, are already documented in the schema. The description reinforces the personId/cellId pairing but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 states a precise verb and resource: removing ONE assignment, defined explicitly as the link between a person and a block with its role and ownership share. It clearly distinguishes this from delete_person, which removes the person altogether, so an agent can tell the two apart without opening schemas.

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 names when to use alternatives: delete_person for removing a person entirely, get_cell_details for listing current assignments, and assign_person for re-creating a removed assignment. The idempotency note also tells the agent what this call does and does not prove.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.