Skip to main content
Glama

graph_add_chat_member

Adds a specified user to a group chat and optionally shares prior chat history from a given ISO 8601 timestamp. Requires delegated ChatMember.ReadWrite permission.

Instructions

Add a user to a group chat.

Requires the delegated ChatMember.ReadWrite permission.

Args: chat_id: The chat ID. user_id: User ID or user principal name to add. share_history_from: ISO 8601 timestamp (e.g. "2026-07-14T12:00:00Z") to share chat history from. Empty shares no history.

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": {
      "chat_id": "<chat_id>",
      "user_id": "<user_id>"
    },
    "name": "graph_add_chat_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
user_idYes
share_history_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the required permission and the side effect of share_history_from (empty shares no history), which are genuinely useful. It omits other behavior an agent needs for a mutation tool: idempotency when the user is already a member, error behavior for invalid IDs, and whether the call is reversible (use graph_remove_chat_member).

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 purpose sentence is front-loaded and the Args block maps cleanly to the three parameters with no padding. The one wasted line is chat_id's restatement, which adds nothing the parameter name does not already convey.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers purpose, permission, and all parameters, but leaves out outcome/return behavior and failure modes. It is adequate rather than complete.

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 description coverage is 0%, so the description must compensate, and it does for most parameters: user_id clarifies it accepts a UPN as well as an ID, and share_history_from documents format, example value, and empty-string behavior. Only chat_id is thin ("The chat ID"), and the optional/required distinction is left to 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?

The description opens with a specific verb plus resource ("Add a user to a group chat"), which is unambiguous. The "group chat" scope also implicitly separates it from member removal and other chat operations, though no sibling is named explicitly.

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?

It gives a useful precondition ("Requires the delegated ChatMember.ReadWrite permission") and scopes the tool to group chats. However, it never says when to prefer this over alternatives such as graph_create_chat for a new conversation, nor does it exclude 1:1 chats or explain re-adding an existing member.

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

Deploy Server

Other Tools