Microsoft 365 MCP Server

format-excel-range

Destructive

Format Excel spreadsheet ranges by adjusting column width, row height, alignment, borders, fonts, and cell protection in Microsoft 365.

Instructions

Update the navigation property format in drives

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": {
      "body": "<body>",
      "driveId": "<driveId>",
      "driveItemId": "<driveItemId>",
      "workbookWorksheetId": "<workbookWorksheetId>"
    },
    "name": "format-excel-range"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`driveId`	Yes	Path parameter: driveId
`driveItemId`	Yes	Path parameter: driveItemId
`workbookWorksheetId`	Yes	Path parameter: workbookWorksheetId
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-developmentMar 25, 2026

TDQS

C2.1/5.0

Behavior2/5

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

Annotations indicate this is a destructive, non-read-only operation, but the description doesn't disclose any behavioral traits beyond what annotations provide. It doesn't mention that this modifies Excel file formatting, potential side effects, authentication requirements, or rate limits. The description adds no meaningful context about the tool's behavior.

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?

The description is a single sentence, which is appropriately concise. However, it's poorly structured and front-loaded with confusing terminology ('navigation property format') that doesn't clearly communicate the tool's purpose. While brief, it fails to efficiently convey essential 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?

For a complex destructive tool with 6 parameters, nested objects, and no output schema, the description is severely inadequate. It doesn't explain what the tool actually does (format Excel ranges), what resources it affects, what the expected outcome is, or any error conditions. The description fails to provide necessary context for proper tool invocation.

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?

With 83% schema description coverage, the input schema already documents most parameters well. The description adds no additional meaning about parameters beyond what's in the schema. It doesn't explain the relationship between parameters or provide usage examples. The baseline score of 3 reflects adequate schema coverage without description enhancement.

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

Purpose2/5

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

The description 'Update the navigation property format in drives' is vague and confusing. It doesn't clearly state that this tool formats Excel ranges (as suggested by the tool name), nor does it specify what 'navigation property format' means. It's essentially a tautology that restates the tool name without clarifying the actual purpose.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing an Excel file in OneDrive), when formatting is appropriate, or how this differs from sibling tools like 'sort-excel-range' or 'get-excel-range'.

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

Deploy Server