Skip to main content
Glama
Sign In
Local MCP

Local MCP

by colibird-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

excel_write_cell

Write a value to a specific cell in an Excel file. Automate spreadsheet updates directly from your AI assistant or local Mac workflows.

Instructions

Writes a value to a specific cell in an Excel file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "excel_write_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.352
  2. Removedv3.0.341
  3. Addedv3.0.165
  4. Removed
  5. Addedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations provided. The description indicates a write operation but discloses no behavioral traits such as file creation, overwrite behavior, or error handling. The lack of parameters also hides how inputs are resolved.

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?

The description is very short, but it is underspecified to the point of being unhelpful. Conciseness is wasted when critical information about parameters is absent.

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 that the tool requires specifying a file, cell, and value to write, and there is no output schema, the description is completely inadequate. It provides no information on how to invoke the tool or what to expect.

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

Parameters1/5

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

The input schema has zero parameters, yet the description implies parameters are needed (file, cell, value). The description adds no meaning beyond the schema and fails to explain how the tool receives inputs. Schema coverage is 100% but irrelevant because parameters are missing.

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?

The description states 'writes a value to a specific cell in an Excel file,' which is clear in verb and resource. However, the input schema has zero parameters, contradicting the implied need to specify file, cell, and value. This mismatch undermines clarity.

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 versus siblings like excel_create or excel_read. No context, prerequisites, or alternative suggestions provided.

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