Skip to main content
Glama
Sign In
OpenPyXL MCP Server

OpenPyXL MCP Server

by jonemo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_content_of_cell_list

Retrieve raw values from multiple specified cells in an Excel sheet by providing the workbook path, sheet name, and cell list. Use it to inspect selected cells without reading the whole workbook.

Instructions

Get the raw values of a list of specific named cells in an Excel workbook.

Args: filepath: The path to the Excel workbook. For example, "~/Downloads/test.xlsx" or "C:\myfolder\myfile.xlsx". If only a filename is provided, the file will be searched for in the Desktop and Downloads folders. sheet_name: The name of the sheet to get the value from. cell_name_list: A list of cell names. For example, ["A1", "B2", "C3"].

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>",
      "sheet_name": "<sheet_name>",
      "cell_name_list": "<cell_name_list>"
    },
    "name": "get_content_of_cell_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYes
sheet_nameYes
cell_name_listYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Get' plus 'raw values' conveys a non-mutating read and the raw-vs-formatted distinction is a genuinely useful detail, but nothing is said about error behavior for invalid cell names, whether results preserve input order, or how missing cells are represented.

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

Conciseness4/5

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

The operational sentence is front-loaded and wastes no words, and the Args block is tightly formatted. The parameter names are repeated verbatim from the schema, which is slightly redundant, but each entry earns its place through added examples and fallback behavior.

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?

For a three-required-parameter read tool with an output schema already documenting return values, the main gaps are behavioral rather than structural. Parameter guidance is strong, but the definition says nothing about partial failures or how many cells can be requested at once, which matters for a list-based call.

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 0%, so the description must compensate, and it largely does: all three parameters are documented with worked examples, including concrete Windows and POSIX path formats and the non-obvious fallback that a bare filename is searched in Desktop and Downloads. It stops short of saying whether cell_name_list accepts ranges or mixed-case names.

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 first sentence states a specific verb and resource with scope: raw values of a list of specific named cells in an Excel workbook. The batch/list scope implicitly distinguishes it from single-cell siblings like get_cell_value, but no sibling is named explicitly, so an agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'a list of specific named cells' suggests use for multiple discrete cells rather than a contiguous block (get_values_of_cell_range) or a single cell (get_cell_value). There is no explicit when-to-use or when-not-to-use instruction, and no mention of what to do if the sheet or file is missing.

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