Skip to main content
Glama
Sign In
unifiles-mcp

unifiles-mcp

by Asheng008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

excel_inspect_file

Inspect Excel file structure to list sheets, headers, and preview rows. Use before selecting a sheet to read.

Instructions

检查 Excel 文件结构。

返回包含所有 Sheet 名称、列头和前几行数据预览的摘要信息。 在决定读取哪个 Sheet 之前，请先使用此工具。

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": {
      "file_path": "<file_path>"
    },
    "name": "excel_inspect_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesExcel 文件路径（支持相对路径和绝对路径）
include_previewNo是否包含数据预览（默认 False，避免数据量大时性能问题）
preview_rowsNo如果 include_preview=True，每个工作表预览的行数（默认 3 行）

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, description carries full burden. It describes return values (sheet names, headers, preview) and mentions performance concern with include_preview. No side effects or destructive actions disclosed, but as a read-only operation, it's adequately transparent.

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?

Description is extremely concise with two sentences, front-loading the main purpose and usage guidance. No wasted words.

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?

Given the tool's low complexity and presence of output schema, the description fully covers purpose, usage, and parameter hints. It is complete for an inspection tool.

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?

Schema description coverage is 100%, so baseline 3. Description adds overall context about return values but does not enhance parameter descriptions beyond what schema provides.

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?

Description clearly states tool checks Excel file structure, returns sheet names, headers, and preview. It distinguishes from sibling tool 'excel_read_sheet' by advising use before reading a specific sheet.

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

Usage Guidelines4/5

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

Explicitly instructs to use before deciding which sheet to read ('在决定读取哪个 Sheet 之前，请先使用此工具。'). However, it does not provide negative guidance or 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