Mencoro

Archive an organization

archive_organization

Destructive

Archive an organization: its projects are archived and stop being checked, its pending invitations are cancelled, and its subscription is cancelled at the end of the billing period. Requires a confirmationToken: call preview_operation with tool "archive_organization" and these arguments first, show the returned plan to the user, and call this tool only after the user explicitly agrees. Needs the organization:manage permission and the owner role.

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": {
      "organizationId": "<organizationId>",
      "confirmationToken": "<confirmationToken>"
    },
    "name": "archive_organization"
  }
}

Input Schema

Name	Required	Description
`requestId`	No	Optional idempotency key, 8-255 printable characters. Reuse it only to retry this same call.
`organizationId`	Yes
`confirmationToken`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`role`	Yes	The caller's current role in this organization
`status`	Yes
`imageUrl`	No
`createdAt`	Yes
`description`	No
`contactEmail`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool as destructive and non-idempotent, but the description adds substantial behavioral detail beyond them: the exact cascading effects on projects, invitations, and subscription billing. It also discloses the required authorization level and the mandatory preview/confirmation protocol.

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 front-loaded with the core action and its consequences, then moves to prerequisites and permissions. It is dense but every sentence carries necessary information, with no 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?

For a destructive organization-level mutation with an output schema present, the description covers the critical missing context: cascade effects, authorization requirements, and the confirmation-token workflow. Return values need not be explained because an output schema exists.

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 only 33%, so the description must compensate. It explains the confirmationToken's origin and required use, but organizationId is left to the obvious parameter name and the requestId semantics remain in the schema.

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 specific verb and resource (archive an organization) and goes further by spelling out the cascade: projects archived, pending invitations cancelled, and subscription cancelled at billing period end. This is clearly distinguishable from sibling tools such as archive_project and restore_organization.

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 gives an explicit prerequisite workflow: call preview_operation first with the same tool name and arguments, show the plan to the user, and only call this tool after explicit agreement. It also names the required permission and owner role, leaving little ambiguity about when and how to invoke it.

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

All Mencoro tools Inspect

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.