Mencoro

Create an organization

create_organization

Create a new organization, owned by the caller. Only with a Mencoro connection that is not limited to one organization. Requires a confirmationToken: call preview_operation with tool "create_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": {
      "name": "<name>",
      "confirmationToken": "<confirmationToken>"
    },
    "name": "create_organization"
  }
}

Input Schema

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

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`status`	Yes	Always active on creation.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover the safety profile (not read-only, not destructive, not idempotent); the description goes well beyond by disclosing the account-scoping constraint, permission/role requirements, the required human-confirmation sequence, and how the confirmationToken is obtained. This is exactly the context an agent cannot infer from structured fields.

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?

Front-loaded with the action and ownership, then the scoping constraint, then the confirmation workflow, then permissions. Every sentence carries required information, though the confirmation-flow sentence is long and could be split for readability.

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 mutation tool with an output schema (so return values need not be described), the description covers the gating condition, auth requirements, and the mandatory preview/confirm workflow. An agent has everything needed to decide whether and how to call it.

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 description coverage is only 33%, so the description must compensate, and it does so for the most critical parameter by explaining that confirmationToken comes from preview_operation and must follow explicit user agreement. The name parameter's constraints (maxLength) are left to the schema, and requestId is already documented there.

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 ('Create a new organization') plus the ownership semantics ('owned by the caller'). This clearly separates it from update_organization, archive_organization, get_organization, and restore_organization in the sibling list.

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?

Gives explicit preconditions: only usable with a Mencoro connection not limited to one organization, requires organization:manage and the owner role, and mandates a preview_operation confirmation flow before invocation. It also names the sibling tool (preview_operation) and the exact argument to pass 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.