Skip to main content
Glama

graph_mark_chat_read

Marks a Microsoft Teams chat as read or unread for a specified user, so you can manage unread status and keep message state accurate.

Instructions

Mark a chat as read or unread for a user.

Args: chat_id: The chat ID. user_id: The user ID to mark the chat for. is_read: Whether the chat is read (default true). Use false to mark it unread.

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_mark_chat_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
is_readNo
user_idYes

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 supplied, the description carries the full disclosure burden, and it does establish that this is a write/state-change operation with a dual direction (read or unread) and a documented default of true. It is silent on permissions required, whether the change is reversible for other participants, and idempotency, which are meaningful gaps for an unannotated mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operation is stated in the first sentence and the parameter meanings follow in a compact list; every line adds information and nothing is redundant. The docstring-style Args block is a readable structure for an agent parsing it.

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 three-parameter, non-nested tool with no output schema, the description covers purpose, all parameters, and the default. The remaining gap is environmental behavior (auth/permission requirements and what happens on an invalid chat_id), which the annotations do not cover either.

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: all three parameters are named and given meaning, including the non-obvious default (is_read defaults to true) and the inverse case ('Use false to mark it unread'). It does not say what format the IDs take or whether user_id must be the caller or can be another user.

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 gives a specific verb and resource ('Mark a chat as read or unread') plus the scope ('for a user'), which is enough to distinguish it from a similarly shaped sibling like graph_mark_mail_read. It stops short of naming that sibling explicitly, so the differentiation is implied by the resource noun rather than stated.

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 guidance on when to use this versus alternatives, no mention of prerequisites (e.g. the caller needing to be a chat member), and no exclusions. The only directional hint, 'Use false to mark it unread', is parameter-level semantics rather than usage guidance.

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