Skip to main content
Glama
Sign In

Kangram

by app.kangram
OverviewDiscussionsAdmin

Add board member

add_board_member

Use this command to add a user directly to a board — they become a member immediately, with no invitation to accept. This is the one-step grant (the bot /addmember command). Owner/admin only; cannot create or assign 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": {
      "board_id": "<board_id>",
      "username": "<username>"
    },
    "name": "add_board_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoRole to assign (admin or user). Default: user. Cannot assign owner role.
board_idYesBoard ID to add the user to.
usernameYesTelegram username of the user to add (without @).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: immediate effect, owner/admin-only authorization requirement, and that the owner role cannot be created or assigned. Annotations already cover safety/idempotency, but the description leaves the non-idempotent behavior (what happens when the user is already a member) undisclosed.

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?

Three short sentences, front-loaded with the core action, with the authorization caveat last. Slight redundancy between 'Owner/admin only' and 'cannot create or assign the owner role', which the schema also states.

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?

Covers what the tool does, the authorization gate, and the role ceiling, which is enough for a simple three-parameter mutation with no output schema. The only gap is behavior when the target is already a member, which matters given idempotentHint=false.

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 coverage is 100%, so all three parameters including the role enum and the 'cannot assign owner role' constraint are already documented. The description echoes the owner-role restriction but adds no new format or usage detail beyond the schema, so the baseline 3 applies.

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 ('add a user directly to a board') and immediately clarifies the semantics: immediate membership with no invitation to accept, which cleanly separates it from invite_board_member 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the selecting condition (direct, one-step grant) and implicitly excludes the invitation flow by noting there is nothing to accept. It would be stronger if it named invite_board_member explicitly as the alternative for invited members.

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