Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Organization

modify_organization

Update an organization's properties, such as its name, by specifying the organization ID and optional new name.

Instructions

Modifie les propriétés d'une organisation.

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": {
      "org_id": "<org_id>"
    },
    "name": "modify_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNouveau nom pour l'organisation (optionnel)
org_idYesL'ID de l'organisation à modifier

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / name / description
      Added value: +"Nouveau nom pour l'organisation (optionnel)"
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation à modifier"
  2. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden; it discloses nothing about permissions or auth requirements, whether renaming is reversible, how partial updates or null values behave, or what happens to existing settings. Only the bare fact of mutation is conveyed, and only through the verb 'Modifie'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, which is structurally clean, but its brevity reflects under-specification rather than economy. Nothing is front-loaded beyond a generic verb.

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

Completeness2/5

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

For a mutation tool with no annotations and no explanation of which properties can be modified or what the behavior is around nulls and permissions, the description is too thin, even though an output schema exists and the parameters are fully documented.

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%, and both parameters (org_id, name) are already fully documented in the schema, including the note that name is optional. The description adds no meaning beyond that, so the baseline of 3 is appropriate.

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

Purpose2/5

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

The description 'Modifie les propriétés d'une organisation' merely restates the tool name and title in French. It names no specific property that can be changed, even though only one mutable field (name) exists in the schema, and it does not distinguish itself from the sibling tool modify_organization_access.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as modify_organization_access for permission changes or delete_organization for removal. The agent must infer the tool's scope entirely from the name.

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