Skip to main content
Glama

create_organization_custom_role

Create a custom gym role from delegable capabilities (confirm-gated). Owner only. Use list_organization_custom_roles for the valid capability keys — billing, roster, payouts and ownership can't be delegated.

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>",
      "name": "<name>",
      "capabilities": "<capabilities>"
    },
    "name": "create_organization_custom_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
descriptionNo
capabilitiesYes
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the authorization requirement (owner only) and a validation constraint that rejects billing, roster, payouts and ownership capabilities — neither is inferable from structured fields. The "confirm-gated" behavior is partly redundant since the confirm parameter's own schema text already explains the preview-only path.

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?

Two tight sentences, front-loaded with the action and its gate, followed by the authorization and validation caveats. No filler or restatement of the tool name.

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 5-parameter mutation tool with no output schema, the essential call-time facts — owner-only access, confirm-to-execute, valid-key source, forbidden capabilities — are all present. What remains unstated are the post-creation return (e.g., the new role's identifier) and error behavior on invalid input, which are secondary but not trivial.

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?

With only 20% schema description coverage, the description carries most of the burden, and it does clarify the riskiest parameter by listing non-delegable capability domains and pointing to the list tool for valid keys. However, it says nothing about name, description, or organizationId, and does not state what happens when an invalid capability key is supplied — so the compensation is partial rather than complete.

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 definition leads with a specific verb and resource ("Create a custom gym role") and immediately narrows the scope to "delegable capabilities," which separates it cleanly from the update/delete/list siblings whose names imply the same resource.

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?

It gives an explicit prerequisite ("Owner only") and routes the agent to list_organization_custom_roles for valid capability keys, which is a real operational dependency. It stops short of stating when to use update_organization_custom_role or delete_organization_custom_role instead, but the create verb leaves little ambiguity.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.