Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

update_person

Destructive

Updates an existing person: ONLY the fields provided are written, the others keep their value. Cannot change id; initials are not editable (the chip is derived from name). tags, when sent, REPLACES the whole list. Changing color also changes the person's level colour. Returns the updated person; returns an error, nothing written, if the id is unknown (find it with search_people). To move someone onto or off a block use assign_person / unassign_person, and delete_person to remove them from the project.

Input Schema

NameRequiredDescriptionDefault
idYesID of the person to update (find it with search_people); it cannot be changed
descNoNew description of the profile
nameNoNew first name or full name
noteNoNew internal notes
roleNoNew professional role
tagsNoREPLACES the whole list of tags (this is NOT an append) — a tag absent from this array is removed; `[]` removes them all. Field omitted: the tags do not change.
colorNoNew hex color (e.g. '#3dffa0'); the level colour follows it
levelNoNew level, free text (e.g. `Élevé`, `Intermédiaire`)
networkNoNew network of belonging (free text, e.g. 'core')
categoryNoNew category: `moteur` (driver / leader), `pivot` (linchpin), `executant` (operational)
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. Changed9 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"New category: `moteur` (driver / leader), `pivot` (linchpin), `executant` (operational)"
    • addedInput schema / properties / color / description
      Added value: +"New hex color (e.g. '#3dffa0'); the level colour follows it"
    • addedInput schema / properties / desc / description
      Added value: +"New description of the profile"
    • addedInput schema / properties / id / description
      Added value: +"ID of the person to update (find it with search_people); it cannot be changed"
    • addedInput schema / properties / level / description
      Added value: +"New level, free text (e.g. `Élevé`, `Intermédiaire`)"
    • addedInput schema / properties / name / description
      Added value: +"New first name or full name"
    • addedInput schema / properties / network / description
      Added value: +"New network of belonging (free text, e.g. 'core')"
    • addedInput schema / properties / note / description
      Added value: +"New internal notes"
    • addedInput schema / properties / role / description
      Added value: +"New professional role"
  2. Changed2 schema fields 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."
    • changedInput schema / properties / tags / description
      Previous value: -"REMPLACE la liste entière des étiquettes (ce n'est PAS un ajout) — un tag absent de ce tableau est retiré ; `[]` les retire toutes. Champ omis : les étiquettes ne changent pas."New value: +"REPLACES the whole list of tags (this is NOT an append) — a tag absent from this array is removed; `[]` removes them all. Field omitted: the tags do not change."
  3. Changed1 schema field changed
    • changedInput schema / properties / tags / description
      Previous value: -"REMPLACE la liste entière des étiquettes (ce n'est PAS un ajout) — un tag absent de ce tableau est retiré ; `[]` les retire toutes. Omets le champ pour ne pas y toucher."New value: +"REMPLACE la liste entière des étiquettes (ce n'est PAS un ajout) — un tag absent de ce tableau est retiré ; `[]` les retire toutes. Champ omis : les étiquettes ne changent pas."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With destructiveHint=true already declaring a mutating profile, the description still adds substantive behavior: partial-write semantics, `id` immutable, initials non-editable and derived from `name`, `tags` replacing the whole list, color cascading to the level colour, and an atomic failure mode ('returns an error, nothing written, if the id is unknown'). This is well beyond what annotations convey.

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?

Roughly five dense clauses, front-loaded with the partial-update rule that matters most, then field caveats, then return/error behavior, then sibling routing. No sentence is filler.

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?

Covers mutation scope, immutability constraints, list-replacement semantics, side effects, success return ('returns the updated person') and the failure mode. With no output schema, that return/error statement is exactly what is needed; nothing an agent requires to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds cross-parameter meaning the schema states only locally — the provided-fields-only rule, tags replacement consequences, and the color/level-colour coupling. It cannot add much more given 11 fully documented parameters.

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?

States a specific verb and resource ('Updates an existing person') and immediately scopes it with partial-update semantics ('ONLY the fields provided are written'). It also distinguishes itself from add_person, delete_person and assign_person/unassign_person by name, so an agent can route without opening sibling 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?

Explicitly routes away from this tool for two adjacent intents: block assignment goes to assign_person / unassign_person, removal goes to delete_person. It also tells the agent how to obtain the required id ('find it with search_people'), covering the only real precondition.

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

All OrgGen AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources