Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

system

Retrieve server information, authenticate with Microsoft Graph API, or check authentication status to manage Microsoft 365 access.

Instructions

System operations: get server info, authenticate with Microsoft Graph API, or check authentication status

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

Input Schema

NameRequiredDescriptionDefault
forceNoForce re-authentication even if already authenticated (for authenticate operation)
operationYesOperation to perform: about (server info), authenticate (connect to MS Graph), check_status (verify auth)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 behavioral burden, and it discloses almost nothing: it does not say that authenticate triggers an interactive sign-in flow, whether it blocks or opens a browser, how tokens persist, or that repeated calls without force are no-ops. The 'Force re-authentication' behavior exists only in the schema, and no failure modes or side effects are described.

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 three compactly enumerated operations and no filler. It is efficiently structured, though the extreme brevity leaves the operational nuance unaddressed rather than genuinely tight.

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?

This is a multi-operation, auth-performing tool with no annotations and no output schema, so the description must explain more than it does. Missing are what authenticate actually does interactively, what check_status returns, and what an agent should do on failure – gaps that matter for a tool that gates access to every Graph-backed sibling.

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 both the operation enum and the force flag are already fully documented in structured data, setting the baseline at 3. The description adds nothing beyond those enum descriptions – it never mentions force, its interaction with authenticate, or that it is ignored for the other operations.

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 the resource (system/server) and enumerates the three concrete operations – server info, authenticate, check auth status – which map one-to-one onto the enum values. An agent can tell this is the auth/system utility rather than a data tool like mail or calendar, though the phrasing is essentially a restatement of the enum.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical glosses ('server info', 'connect to MS Graph', 'verify auth') suggest which operation applies to which situation but state no explicit when-to-use, prerequisites, or exclusions. There is no guidance such as 'call check_status before any Graph-backed tool' or 'authenticate only if check_status reports unauthenticated', which is exactly the sequencing an agent needs here.

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