Skip to main content
Glama
Alex-eng-ux

Office MCP Server

by Alex-eng-ux

Read Excel File

office_read_excel
Read-onlyIdempotent

Read Excel (.xlsx) data using file path, optional sheet name, and cell range. Outputs headers and rows in a structured format.

Instructions

Read data from an Excel (.xlsx) file.

Args:

  • filePath (string): Absolute or relative path to the Excel file

  • sheetName (string, optional): Name of the sheet to read. Defaults to first sheet

  • range (string, optional): Cell range to read, e.g. "A1:C10". Reads all data if not specified

Returns: { "sheetName": string, "headers": string[], "rows": object[], "totalRows": number, "totalColumns": number }

Examples:

  • Use when: "Read the sales data from report.xlsx"

  • Use when: "What are the column headers in Sheet2 of data.xlsx?"

  • Don't use when: You need to write data to Excel (use office_write_excel instead)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file (e.g., 'C:/data/report.xlsx' or './report.xlsx')
sheetNameNoSheet name to read (defaults to first sheet)
rangeNoCell range like 'A1:C10' (reads all if not specified)
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the return format structure and default behaviors (first sheet, full range if unspecified), enriching transparency beyond 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?

The description is well-structured with Args, Returns, and Examples sections. Every sentence adds value without redundancy.

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

Completeness5/5

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

Despite no output schema, the description fully documents the return format. All parameters are covered in both schema and description, making it complete for agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds context like absolute/relative path, default sheet, and range example, providing slight additional value.

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

Purpose5/5

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

The description clearly states 'Read data from an Excel (.xlsx) file,' identifying the specific verb and resource. It distinguishes from siblings via the 'Don't use when' note referencing office_write_excel.

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

Usage Guidelines5/5

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

Explicit 'Use when' and 'Don't use when' guidance is provided, including a direct alternative (office_write_excel) for writing scenarios.

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/Alex-eng-ux/office-mcp-server'

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