Excel MCP Server

by ishayoyo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get_range

Extract cell values from specified ranges in Excel or CSV files to access spreadsheet data for analysis or processing.

Instructions

Get values from a range of cells

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": {
      "filePath": "<filePath>",
      "startCell": "<startCell>",
      "endCell": "<endCell>"
    },
    "name": "get_range"
  }
}

Input Schema

Name	Required	Description
`filePath`	Yes	Path to the CSV or Excel file
`startCell`	Yes	Start cell in A1 notation (e.g., "A1")
`endCell`	Yes	End cell in A1 notation (e.g., "D10")
`sheet`	No	Sheet name for Excel files (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Get values' but does not specify whether this is a read-only operation, what happens with invalid ranges, if it requires file permissions, or the format of returned data. This leaves significant gaps in understanding the tool's behavior and limitations.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to grasp quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the tool returns (e.g., data format, error handling) or behavioral aspects like performance or constraints. For a tool with 4 parameters and no structured output information, more context is needed to ensure proper usage.

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?

The description does not add meaning beyond the input schema, which has 100% coverage with clear descriptions for all parameters. Since the schema fully documents the parameters, the baseline score of 3 is appropriate, as the description neither compensates for gaps nor enhances understanding of the parameters.

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 clearly states the action ('Get values') and resource ('from a range of cells'), making the purpose understandable. However, it does not distinguish this tool from similar siblings like 'get_cell' or 'read_file', which might also retrieve data from files, leaving some ambiguity about its specific role.

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

Usage Guidelines2/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. With many sibling tools like 'get_cell', 'read_file', and 'filter_rows' that might overlap in functionality, there is no indication of context, prerequisites, or exclusions for using 'get_range'.

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