rename_orgRename an organization (the personal org is frozen).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | New organization name. | |
| orgId | Yes | Organization id (uuid). |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already include destructiveHint=true, which covers the mutation risk. The description adds the 'personal org is frozen' constraint, which is useful behavioral context. However, it does not explain side effects, reversibility, or what happens if attemted on a frozen org, so it only partially goes 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that states the operation and the key restriction in an immediately digestible way. Every word contributes meaning, with no filler or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with two required parameters, full schema coverage, a destructiveHint, and an output schema, the description is nearly complete. It covers the core operation and the main caveat. The only minor gap is not explicitly spelling out that the personal org cannot be renamed as a direct instruction, but the parenthetical conveys this adequately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both 'name' and 'orgId' clearly. The description adds no additional parameter-level detail, such as format constraints or relationship between parameters. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Rename') and resource ('organization'), which clearly identifies the operation. It also adds a meaningful constraint ('the personal org is frozen') that distinguishes this from generic org management operations and prevents misuse. The sibling-tool set further confirms this is the dedicated rename operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: use this to rename an organization, but not a personal org because that org is frozen. It does not explicitly list alternative tools, but given the siblings, no direct alternative for renaming exists. The frozen-org note acts as a useful when-not condition.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, and the descriptions clearly explain boundaries. However, list_diagrams/list_documents and get_board/get_board_image are two pairs that both concern the same underlying resource, so an agent could initially select the wrong one without reading carefully.
Nearly all tool names are snake_case verb_noun pairs such as create_project, update_document, and unpublish_listing, which is very consistent. The exceptions are bare 'draw' and the non-pattern 'whoami', so it is not a perfect 5.
With 38 tools, the surface exceeds the 25+ threshold and spans orgs, projects, documents, board drawing, membership, and marketplace publishing. While each subdomain is individually reasonable, the aggregate is heavy and likely to overwhelm an agent; several related actions could be grouped or exposed more sparingly.
The set covers the main lifecycle: org/project/document CRUD, board rendering and editing, member management, and template publish/use/update. Minor gaps remain—there is no get_project single-resource read, and groups/links/notes are manipulated only through the generic update_board rather than dedicated tools—but these are workable.