Skip to main content
Glama
Sign In
Microsoft Graph MCP Server

Microsoft Graph MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_external

Find external items in a specific Microsoft Graph connector using the connection ID and query.

Instructions

Search a specific Microsoft Graph connector (externalItem).

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>",
      "connection_id": "<connection_id>"
    },
    "name": "search_external"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'Search' implies a read-only operation, but there is no explicit mention of side effects, result formatting, pagination, or error behavior, leaving significant behavioral ambiguity.

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 description is a single, focused sentence with no redundant words, effectively communicating the tool's essence in a compact form.

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?

The description covers only the basic purpose. It lacks parameter details, usage context, output expectations, and any edge-case behavior, making it incomplete for an agent to confidently invoke the tool without additional information.

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

Parameters2/5

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

Parameter names are self-explanatory to a degree (query, connection_id, size), but no parameter descriptions are provided. The description does not clarify what connection_id refers to, what a valid query looks like, or how size affects results, leaving key semantics underspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Search' and the specific resource 'Microsoft Graph connector (externalItem)', making the tool's core purpose unmistakable. This also distinguishes it from sibling search tools like search_files or search_messages via the explicit connector scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or contextual conditions mentioned. The description only states what it does, not when it should be chosen.

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