Skip to main content
Glama
Sign In

Kangram

by app.kangram
OverviewDiscussionsAdmin

Update member role

update_member_role

Use this command to change an existing board member's role. Owner/admin only. Cannot target the board owner or promote anyone to owner.

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

Input Schema

NameRequiredDescriptionDefault
roleYesNew role to assign (admin or user). Cannot assign owner.
user_idYesUser ID of the member whose role to change.
board_idYesBoard ID where the member belongs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish this is a non-read-only, non-destructive, non-idempotent mutation, so the bar is lower. The description adds genuinely useful behavior beyond that: the required caller privilege level and two hard validation constraints (owner target, owner promotion).

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?

Three compact sentences, front-loaded with the operation and immediately followed by the two constraints that most affect invocation. No filler.

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 three-parameter mutation with full schema coverage and annotations, the description covers what is needed to invoke it correctly. It omits only minor context such as what happens to the target user's prior role or any side effects on permissions.

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?

Schema description coverage is 100%, including an enum-limited role field that already documents "Cannot assign owner." The description restates that constraint but adds no new format or syntax detail, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("change an existing board member's role"), which clearly separates it from add_board_member/remove_board_member and from update_namespace_member_role by scope. It stops short of explicitly naming the sibling alternative, so it lands at 4 rather than 5.

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 concrete usage conditions: "Owner/admin only" and "Cannot target the board owner or promote anyone to owner." That is clear guidance on when the call will succeed, though it does not explicitly route the agent to an alternative tool for the excluded cases.

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

All Kangram 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