Skip to main content
Glama

graph_get_primary_channel

Retrieve a Microsoft Teams team's primary General channel by team ID to use the default channel without listing every channel.

Instructions

Get a team's primary channel, the one named General.

Use this as a shortcut for the default channel instead of listing every channel in the team.

Args: team_id: The team ID (from graph_list_teams).

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": {
      "team_id": "<team_id>"
    },
    "name": "graph_get_primary_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Get' implies a non-mutating retrieval, which is the main behavioral signal, but it says nothing about what happens when no channel named General exists, what permissions are required, or what object is returned.

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?

Three short lines, front-loaded with the purpose, followed immediately by the usage rule and the single argument. No redundant restatement of the tool name and nothing that fails to earn its place.

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 simple single-parameter read tool this covers the essentials, but with no output schema and no annotations, the description should at least sketch the return value or the missing-channel behavior. Those gaps are minor but real for an agent deciding whether to call it.

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 0%, so the description must compensate; it does add the provenance hint '(from graph_list_teams)' for team_id, which is real value beyond the bare string type. However, it says nothing about format or validation of the ID, so it only partially fills the coverage gap.

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 ('Get a team's primary channel') and pins down the ambiguous term by defining it as 'the one named General'. That disambiguation is genuinely useful, though no sibling tool is named as the contrast, so it stops short of a 5.

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?

Explicitly tells the agent when to prefer this tool: 'Use this as a shortcut for the default channel instead of listing every channel in the team.' That is clear usage context, but it names no concrete alternative tool and gives no exclusion case (e.g., teams without a General channel).

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