Skip to main content
Glama
Sign In
Excel MCP Server

Excel MCP Server

by SuperPyonchiX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

add_formula

Insert formulas into specified Excel cells using file path, sheet name, and cell position. Automates Excel calculations for data manipulation and analysis.

Instructions

セルに数式を追加します

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>",
      "sheetName": "<sheetName>",
      "cell": "<cell>",
      "formula": "<formula>"
    },
    "name": "add_formula"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellYesセル位置（例: A1）
filePathYesExcelファイルのパス
formulaYes数式（=SUM(A1:A10)など、=で始まる）
sheetNameYesワークシート名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('adds a formula') but doesn't cover critical aspects like whether this overwrites existing cell content, requires file permissions, has side effects, or returns any confirmation. For a mutation tool with zero annotation coverage, this is a significant gap.

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 in Japanese that directly states the tool's function. It's front-loaded with the core action and has no wasted words, making it highly concise and well-structured for quick comprehension.

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 tool's complexity (a mutation operation with 4 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral traits, usage context, or what happens post-execution (e.g., success confirmation or error handling), leaving the agent under-informed.

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 adds no parameter semantics beyond what the input schema provides. Since schema description coverage is 100% (each parameter has a clear description in Japanese), the baseline is 3. The tool description doesn't compensate with additional context like formula syntax examples or file path requirements.

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 'セルに数式を追加します' (Adds a formula to a cell) clearly states the verb ('adds') and resource ('formula to a cell'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'set_cell_value' or 'set_range_values', which might also modify cell content, so it's not a perfect 5.

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. It doesn't mention prerequisites (e.g., file must exist), exclusions, or compare it to siblings like 'set_cell_value' for non-formula content. This leaves the agent guessing about appropriate contexts.

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

Related Tools