Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

teams_channel

Manage Microsoft Teams channels by listing, creating, updating, or deleting channels and handling messages, members, and tabs through Microsoft Graph.

Instructions

Teams channel operations: list, create, get, update, delete channels and manage messages, members, and tabs

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": {
      "operation": "<operation>"
    },
    "name": "teams_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesThe operation to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it says nothing about what delete/remove_member actually destroy, whether it is reversible, what auth or admin rights are needed, or any rate limits. The only behavioral signal is the presence of mutating operation names in the list.

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?

One front-loaded sentence that enumerates scope without filler; nothing is redundant. It is terse to the point of being an inventory rather than an explanation, but no sentence wastes space.

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?

A 13-operation multiplexer with no annotations and no output schema needs at least per-operation context (required identifiers, return shape, side effects); the description provides none. Given the breadth of what it claims to do, the definition is far too thin for an agent to invoke the right operation confidently.

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 coverage is reported as 100%, but the sole parameter's description is the tautology 'The operation to perform', so the schema adds little. The description contributes by grouping the 13 enum values into channel/message/member/tab categories, but it never explains the arguments each operation would need (channel id, member id, tab payload), leaving that entirely unspecified.

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?

Names a specific resource (Teams channels) and enumerates the operation families (list/create/get/update/delete, messages, members, tabs), so an agent can tell this is the channel-level tool rather than teams_chat. It stops short of saying how it differs from sibling teams_chat beyond the resource word.

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?

No guidance on when to use this instead of teams_chat, teams_meeting, or the directory tools, and no prerequisites (permissions, channel must exist, etc.). The enumeration of operations only implies usage; the agent must infer routing from the resource name alone.

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