Skip to main content
Glama

graph_update_chat_topic

Set a group chat's topic to rename it. Only group chats support topics; one-on-one chats are rejected by Microsoft Graph.

Instructions

Rename a chat by setting its topic.

Only group chats have a topic; Graph rejects this for one-on-one chats.

Args: chat_id: The chat ID. topic: New topic for the chat.

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>",
      "topic": "<topic>"
    },
    "name": "graph_update_chat_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
chat_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one important failure mode (the call errors on one-on-one chats), but says nothing about required permissions, whether an empty topic clears or errors, or what the response contains for a mutation tool.

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 plus a compact Args block, with the action front-loaded and the key constraint immediately after. The Args block mostly duplicates the schema and is the only excess.

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 two-parameter mutation with no output schema and no annotations, the description covers the main hazard (non-group chats) but leaves permission requirements, validation of the topic string, and return behavior unaddressed.

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 0%, so the description must supply meaning for both parameters. The Args section repeats the names with near-tautological glosses ('chat_id: The chat ID', 'topic: New topic for the chat'), adding little, though the group-chat constraint does add real semantics about the acceptable topic value.

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 names a concrete verb and resource ('Rename a chat by setting its topic') and implicitly separates itself from siblings such as graph_update_chat_message and graph_update_channel_message by scoping the operation to the chat's topic. It stops short of explicitly naming a sibling it must not be confused with, but an agent can still tell what this does at a glance.

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 supplies a real applicability rule: only group chats have a topic, and Graph rejects the call for one-on-one chats. That is a genuine when-to-use/when-not-to-use condition. It does not point to any alternative tool for non-group chats, which keeps it below a 5.

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