Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Update organisation member role

update_organisation_member_role
Destructive

Change a member's organisation role (the twin of ankra org member role). Needs members.manage. user_id comes from list_organisation_members. role is member, admin, read-only, or project to limit the member to one project (project_id, and project_role_slug defaulting to member). Refused for your own role, for a role carrying a permission you do not hold, for a member stronger than you, for demoting the organisation's last owner, and for limiting an owner to a project. Moving a member to project-only retires their organisation-wide assignments.

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": {
      "user_id": "<user_id>",
      "role": "<role>"
    },
    "name": "update_organisation_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe new organisation role, or project for a project-only membership.
user_idYesThe member's id, as list_organisation_members shows it.
project_idNoUUID of the project, required with role project and refused otherwise (from list_projects).
project_role_slugNoThe built-in role held in the project with role project; member when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds substantial value beyond them: the privilege preconditions, the five refusal cases (self, escalation, stronger member, last owner, owner-as-project-only), and the side effect that project-only moves retire organisation-wide assignments. This is exactly the class of information an agent needs before attempting a privileged mutation.

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?

Dense and front-loaded: purpose, permission, parameter sourcing, enum meaning, and refusal conditions in a few tight sentences with no filler. The heavy use of parentheses makes it slightly harder to scan than a sentence-per-idea layout, but nothing is wasted.

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 four-parameter privileged mutation with no output schema, the description covers what changes, what is destroyed by a project-only move, who may call it, and every documented refusal path. An agent has everything required to decide whether to invoke and to predict the outcome.

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 goes further by explaining what the 'project' enum value means for the role parameter, that project_id accompanies it, and that project_role_slug defaults to member. It does not restate the UUID format of project_id, which the schema already covers.

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 ('Change a member's organisation role') with the scope of the target object clear. The parenthetical CLI twin is minor but the sentence alone lets an agent distinguish this from invite_organisation_member, remove_organisation_member, and list_organisation_roles.

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?

Explicitly states the required permission (members.manage) and where user_id comes from (list_organisation_members), and enumerates the conditions under which the call is refused. It stops short of routing the agent to a sibling for those refused cases (e.g. list_organisation_roles to check a role's permissions first), but the context needed to decide whether to attempt the call is present.

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

All Ankra toolsInspect
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.

Resources