Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

search

Find Microsoft 365 content using KQL or natural language, then filter, sort, and aggregate results by file type, date, site, and people.

Instructions

Powerful unified search across Microsoft 365 with intelligent features, aggregations, and content enrichment

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": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoPagination offset (default: 0)
limitNoMax results (default: 25, max: 500)
queryYesSearch query (supports KQL syntax and natural language)
siteIdNoSearch within specific SharePoint site
sortByNoSort configuration
filtersNoAdditional KQL filters
dateRangeNoDate range filter
fileTypesNoFilter by file extensions (e.g., ['docx', 'xlsx', 'pdf'])
aggregateByNoFields to aggregate for filters (default: fileType, lastModifiedBy)
entityTypesNoTypes to search (default: driveItem, listItem). Note: message/event cannot be combined with driveItem/listItem
peopleSearchNoEnable people-specific search mode
enrichContentNoExtract additional content and metadata (default: true)
includeExcelDataNoExtract Excel workbook structure (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It offers only vague phrases ('intelligent features, aggregations, and content enrichment') and discloses nothing about permissions, whether results are read-only, pagination limits, rate limits, or what the response shape looks like for a 13-parameter search tool.

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

Conciseness3/5

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

It is a single front-loaded sentence, which is efficient in shape, but a meaningful share of the words are filler adjectives ('Powerful', 'intelligent features') that convey no actionable information.

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 13 parameters, nested objects, no annotations, and no output schema, a one-line marketing sentence is far too thin. The agent gets no sense of result shape, entity-type constraints, or cost of broad queries, all of which matter for a unified search tool.

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 description coverage is 100%, so each parameter is already documented in the schema, including the important note that message/event cannot be combined with driveItem/listItem. The description adds essentially nothing beyond a loose nod to 'aggregations' and 'content enrichment', so the baseline 3 applies.

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

Purpose3/5

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

The description says it is a search over Microsoft 365, which gives the agent a resource and a verb. But the framing leans on marketing language ('Powerful unified search', 'intelligent features') rather than naming what is actually searchable (files, messages, events, people) or how it relates to the workload-specific siblings like files, mail, or teams_chat.

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 or when-not-to-use guidance. The word 'unified' hints that this is a cross-workload search rather than a single-source one, but nothing tells the agent when to pick this over the files, mail, or contacts siblings, nor what prerequisites apply.

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