Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

import_org

Destructive

Imports an org chart from an indented text outline (one line per block, the indentation sets the hierarchy — e.g. "- Holding\n - Subsidiary A\n - BU1"). Each depth gets a default type (root='groupe' (group), level 1='filiale' (subsidiary), level 2='sous-filiale' (sub-subsidiary), level 3+='node') — adjustable afterwards with update_cell. Mode 'replace' (default) replaces the whole existing org chart. Mode 'merge' adds the blocks that are missing by name without touching the existing ones. The placement is recomputed automatically after the import (equivalent to auto_layout_org).

Input Schema

NameRequiredDescriptionDefault
modeNo'replace' (default) replaces the whole existing org chart (kind='org') with the imported outline. 'merge' adds the blocks that are missing by name (case- and whitespace-insensitive) without touching the existing ones — a block already present is reused as the parent of its new children.
textYesThe indented outline to import, one line per block (e.g. "- Holding\n - Subsidiary A\n - BU1"). The indentation sets the hierarchy.
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. Changed3 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 / mode / description
      Previous value: -"'replace' (défaut) remplace tout l'organigramme existant (kind='org') par le contour importé. 'merge' ajoute les blocs absents par nom (insensible à la casse/espaces) sans toucher aux existants — un bloc déjà présent est réutilisé comme parent pour ses nouveaux enfants."New value: +"'replace' (default) replaces the whole existing org chart (kind='org') with the imported outline. 'merge' adds the blocks that are missing by name (case- and whitespace-insensitive) without touching the existing ones — a block already present is reused as the parent of its new children."
    • changedInput schema / properties / text / description
      Previous value: -"Le contour indenté à importer, une ligne par bloc (ex: « - Holding\\n  - Filiale A\\n    - BU1 »). L'indentation détermine la hiérarchie."New value: +"The indented outline to import, one line per block (e.g. \"- Holding\\n  - Subsidiary A\\n    - BU1\"). The indentation sets the hierarchy."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description reinforces this with the concrete consequence: mode 'replace' (default) replaces the whole existing org chart, while 'merge' leaves existing blocks untouched. It also discloses the automatic post-import layout recomputation, adding behavior beyond the annotations.

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?

Single dense paragraph that front-loads purpose and the input format before modes and side effects. Every sentence carries information, though the type-mapping parenthetical makes it longer than strictly necessary.

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 destructive, no-output-schema import tool, the description covers input format, mode semantics, resulting type assignment, and the automatic layout side effect. It does not mention error/refusal behavior for expectedProjectId, but that is documented in the schema.

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, but the description adds genuine meaning: the per-depth default type mapping (root='groupe', level 1='filiale', level 2='sous-filiale', level 3+='node') is behavior the schema does not convey. expectedProjectId is left to the schema, which documents it adequately.

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 ('Imports an org chart from an indented text outline') and immediately scopes it with a concrete format example. It is clearly distinguishable from the other import_* siblings (import_arch_diagram, import_data_model, import_tasks) because the resource and input format are named.

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

Usage Guidelines4/5

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

The description explains the two modes and their selection criteria ('replace' is the default and wipes the chart; 'merge' only adds missing blocks), and routes follow-up editing to update_cell. It gives clear operational context but never states explicitly when to prefer this tool over the sibling import_* tools.

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