Skip to main content
Glama
Sign In
OpenPyXL MCP Server

OpenPyXL MCP Server

by jonemo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_list_of_sheets

Retrieve worksheet names and dimensions from an Excel workbook by filepath, so you can inspect its structure before reading or analyzing data.

Instructions

Get a list of sheets in an Excel workbook. Each line contains a sheet's name and dimensions.

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.

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>"
    },
    "name": "get_list_of_sheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the filepath resolution fallback (searching Desktop and Downloads when only a filename is given) and the per-line return shape, but says nothing about error behavior for a missing or corrupt file, permission requirements, or whether large workbooks are handled differently.

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 purpose is front-loaded in one sentence and the argument block follows with no padding. The two example paths in the args section are borderline redundant but do real work for path formatting.

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

Completeness4/5

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

For a one-parameter read tool with an output schema present, the definition covers purpose, argument meaning, and return shape well enough to invoke correctly. The remaining gaps concern failure modes, which the output schema does not cover either.

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% and the single filepath property has no description, so the description fully supplies its meaning: path formats for both POSIX and Windows plus the filename-only search fallback. That is a meaningful addition beyond the bare string type, though nothing is said about relative vs absolute path edge cases.

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: 'Get a list of sheets in an Excel workbook,' which is unmistakably distinct from the cell-level siblings (get_cell_value, get_values_of_cell_range). It stops short of explicitly naming a sibling as the alternative, so it is clear but not maximally differentiated.

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 only implied: an agent can infer this is the discovery step that precedes reading cell values, but the description never says when to prefer it or what to do afterward. There are no exclusions, prerequisites, or named alternatives.

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