Skip to main content
Glama

Raw Microsoft Graph Request

graph_query
Destructive

Execute arbitrary Microsoft Graph API requests for Microsoft 365 operations not covered by other tools, supporting custom paths, methods, headers, and request bodies.

Instructions

Execute an arbitrary Microsoft Graph API query. Use this for operations not covered by other tools.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "graph_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body as a string
pathYesGraph API path (e.g., /me/memberOf)
methodYesHTTP method: GET, POST, PUT, PATCH, or DELETE
headersNoExtra request headers, e.g. { "If-Match": "<etag>" } for concurrency-controlled writes
versionNoAPI version: v1.0 or beta (default: v1.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is supplied externally. The description adds no behavioral context of its own — nothing about what a DELETE/PATCH can destroy, whether changes are reversible, permission/consent requirements, throttling, or how failures surface. For an unconstrained escape-hatch tool this is a meaningful omission, though it stops short of contradicting the annotations.

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?

Two sentences, zero waste, and the routing rule ('use this for operations not covered by other tools') is front-loaded right after the purpose statement. Nothing to trim.

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?

There is no output schema, so the description should ideally say what comes back (raw Graph JSON, error shape) and whether the caller must handle pagination or etags manually. Given full schema coverage and annotations that already flag destructiveness, the definition is minimally serviceable, but an agent still has to guess at response semantics for a high-risk raw-request 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%, with method, path, version, headers and body all documented in the schema itself, including an If-Match concurrency example and a v1.0/beta enum. The description contributes nothing beyond that, so the baseline of 3 applies.

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 ('Execute an arbitrary Microsoft Graph API query') and explicitly positions itself as the fallback for 'operations not covered by other tools', which distinguishes it from the enumerated siblings. It stops short of naming concrete example operations or clarifying scope limits (e.g. that it targets Graph endpoints only), but the core purpose is unmistakable.

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?

Gives an explicit use condition: reach for this only when a dedicated tool does not cover the operation. It does not say when NOT to use it (e.g. prefer typed tools whenever available, avoid for bulk loops) or note prerequisites such as required Graph scopes, so the guidance is clear but one-sided.

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