Skip to main content
Glama

graph_search_messages

Search Microsoft Teams chats and channels by keyword to find specific messages, conversations, and decisions across your organization's workspaces.

Instructions

Search messages across Teams chats and channels.

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": {
      "query": "<query>"
    },
    "name": "graph_search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.6/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 disclosure burden, yet it says nothing about result ordering, whether search is keyword or KQL, pagination, or that this is a read-only operation. For a cross-workload search tool the behavioral surface is essentially undocumented.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the efficiency comes partly from omitting information rather than from tight editing of a complete description.

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?

With no annotations, no output schema, and zero parameter documentation, the one-sentence description leaves too much open for a two-parameter search tool. An agent cannot tell what `top` does, how many results to expect, or what a result record contains.

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

Parameters1/5

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

Schema description coverage is 0%, so both parameters rely on the description, which mentions neither. The `top` parameter in particular is completely unexplained, and its unusual minimum of -9007199254740991 gives no hint of valid intent; the description does not compensate for the coverage gap at all.

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 specific verb (Search), a specific resource (messages), and a scope (Teams chats and channels), so an agent can distinguish it from the get-style siblings like graph_get_chat_messages. It stops short of explicitly contrasting itself with those siblings, which keeps it out of the 5 band.

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, when-not-to-use, or alternative routing guidance. The description never says when to prefer this over graph_get_chat_messages, graph_get_channel_messages, or graph_search_all, leaving the agent to infer selection from the tool name alone.

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