Skip to main content
Glama

sort-excel-range

Destructive

Sort a range in an Excel worksheet. Specify the workbook, worksheet, and range to organize data.

Instructions

Update the navigation property sort in drives

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
driveIdYesPath parameter: driveId
driveItemIdYesPath parameter: driveItemId
workbookWorksheetIdYesPath parameter: workbookWorksheetId
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior1/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description adds no behavioral context. It does not explain what the operation does beyond a vague 'update navigation property', which is confusing and uninformative.

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

Conciseness2/5

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

Extremely short but also incorrect. Conciseness is not valuable when the content is misleading. It should be replaced with an accurate, informative description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a complex operation like sorting Excel ranges, the description fails to provide essential context. The tool cannot be used correctly based on this definition.

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?

The input schema has descriptions for most parameters (83% coverage), but the tool description adds no additional meaning. The 'body' parameter is critical for specifying sort criteria, but its contents are not explained.

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

Purpose1/5

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

The description says 'Update the navigation property sort in drives', which is unrelated to sorting an Excel range. The tool name suggests sorting an Excel range, but the description does not match. It is misleading and fails to state 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?

No guidance on when to use this tool vs alternatives like format-excel-range or clear-excel-range. The description provides no context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Softeria/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server