Skip to main content
Glama
Sign In

Kangram

by app.kangram
OverviewDiscussionsAdmin

Invite board member

invite_board_member

Use this command to invite a user to a board. The invited user will receive a notification and must accept. Owner/admin only.

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": "invite_board_member"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare that this is a mutation with non-destructive, non-idempotent semantics. The description adds useful behavioral context beyond that: the invitee receives a notification and must accept, and the caller must be owner/admin.

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?

The description is short and front-loaded: purpose first, then acceptance behavior, then permission requirement. Minor filler in 'Use this command to' keeps it from being maximally tight.

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 simple three-parameter invitation tool with a complete schema and annotations, the description supplies the key flow and permission context. It leaves some invitation edge cases and sibling differentiation implicit, but is broadly sufficient to invoke correctly.

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%, so all three parameters are already documented in the input schema. The description adds no additional parameter meaning or formatting guidance beyond the schema.

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?

State a specific verb and resource: invite a user to a board. Clear enough to act on, but it does not distinguish itself from the close sibling add_board_member.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage through 'Use this command to invite' and states an owner/admin prerequisite. It does not explicitly say when to choose this instead of add_board_member or otherwise route the agent among closely related invitation tools.

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