Skip to main content
Glama

excel_write_cell

Write data to Excel cells. Set cell values in a spreadsheet to automate data entry.

Instructions

Write data to Excel cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:68-68 (registration)
    The tool 'excel_write_cell' is registered in the TOOLS array as part of the MCP server definition. However, this is a stub/inspection server — the actual implementation lives in a native binary ('Local MCP' v3.0.163) that is not present in this codebase. The stub simply returns a placeholder message.
    ["excel_write_cell", "Write data to Excel cells"],
  • The handler for all tools (including excel_write_cell) is a generic async function that returns a stub message. The real handler logic is in a separate native binary and not available in this codebase.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it 'writes' without mentioning side effects, permissions, errors, or how data is supplied. With zero parameters, the agent has no clue about expected inputs.

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

Conciseness2/5

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

Extremely concise but at the cost of clarity. The single sentence does not front-load key information and does not earn its place due to vagueness.

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

Completeness1/5

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

Given the tool's write nature and lack of parameters, the description is grossly incomplete. It should explain expected data source, cell targeting, and behavior but provides none of that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no parameters, so the description should clarify how the tool operates without explicit input. It fails to do so, leaving the agent to guess. Baseline for 0 params is 4, but the description adds no meaning, leading to a deduction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Write data to Excel cells' is almost a tautology with the tool name. It provides no specificity about which cells, what data, or how data is provided, and fails to distinguish from other write tools like word_append.

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

Usage Guidelines1/5

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

No guidance on when to use this tool, prerequisites, or how it differs from siblings like excel_create or excel_read. The description offers no usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server