Skip to main content
Glama

graph_create_chat

Creates a new one-on-one or group chat in Microsoft Teams with specified members, optionally adding a topic for organized conversations.

Instructions

Create a new chat (one-on-one or group).

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_type": "<chat_type>",
      "members": "<members>"
    },
    "name": "graph_create_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
membersYes
chat_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not say whether creating a chat with existing members is idempotent or creates a duplicate, what permissions or member identity format are required, or whether the created chat is returned; the title sentence is the only behavioral content.

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?

A single short sentence, front-loaded with the verb and resource with zero filler. It is efficient but arguably over-trimmed given how much parameter and behavior detail is missing.

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

Completeness2/5

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

For a creation tool with two required parameters, 0% schema coverage, no annotations, and no output schema, this description is far too thin. An agent cannot determine valid chat_type values, member identifier format, or side effects from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. It gestures at chat_type via "one-on-one or group" but gives no accepted values, and says nothing about the required members array format or the optional topic default of an empty string.

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?

States a specific verb and resource ("Create a new chat") and adds scope ("one-on-one or group"), which distinguishes it from sibling tools like graph_create_channel or graph_create_contact that create other resource types.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as graph_get_chat or graph_add_chat_member for existing chats. The parenthetical hint about one-on-one versus group implies a mode choice but never explains how to select it.

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