Skip to main content
Glama

Provision board identity

provision_board_identity
Destructive

Provision the organisation's board service principal - the acting identity platform-created agents (created_by 'system') act as when they work AI board tickets. Without it those agents are refused with 'no acting identity that can write' and designating them is refused too; provisioning is the fix that makes the organisation's designated board workers staffable on the next dispatcher cycle. Organisation administrators only. The optional role_slug narrows the principal's powers: 'operator' (the default day-2 operations profile), 'member', or 'viewer'; owner and admin are refused so no agent can hold organisation administration, and custom roles must be assigned from the roles page where their permissions are visible. Provisioning an organisation that already holds a live board identity is a no-op that reports the existing grant unchanged. Granting an identity that can change infrastructure is the same class of decision as giving a colleague the operator role, so this is confirmation-gated in chat. Stand the identity down from the portal's AI settings, which drops the principal to the viewer floor without deleting its audit trail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "provision_board_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_slugNoBuilt-in role the principal holds (default 'operator'). Owner and admin are never accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior2/5

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

The description does real work beyond the annotations: it states the privilege class of the grant, that it is confirmation-gated in chat, and how to reverse it. However, it explicitly claims "provisioning an organisation that already holds a live board identity is a no-op that reports the existing grant unchanged", which is idempotent semantics and conflicts with the supplied idempotentHint=false; an agent could rely on that no-op claim and repeat the call.

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?

Purpose and the failure it fixes are front-loaded, and every sentence carries operational content. The cost is density: several sentences are long semicolon-chained clauses, so a reader has to work harder than necessary to extract the when-to-use rule.

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 single optional-enum, no-output-schema mutation, the description covers actor permissions, the condition that warrants it, the no-op case, the confirmation gate, the privilege ceiling, and the reversal path. Nothing an agent needs to decide whether and how to call it is missing.

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 meaning the enum cannot: 'operator' is the default day-2 profile, owner and admin are refused so no agent can hold organisation administration, and custom roles must be assigned from the roles page. That is genuine semantic value above the schema's enum listing.

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?

A specific verb plus resource ("Provision the organisation's board service principal") is immediately qualified with what that principal is and which actors it serves. It also implicitly separates itself from the sibling designate_board_worker by describing the failure mode ("designating them is refused too") that this tool resolves.

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?

Explicit preconditions and triggers: "Organisation administrators only", use it when agents are refused with 'no acting identity that can write', and it makes the designated workers staffable on the next dispatcher cycle. It also covers the already-provisioned case (no-op reporting the existing grant) and the inverse path (stand down via the portal's AI settings), which is the right routing for the opposite intent.

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.