Skip to main content
Glama

Edit your Markdown Spreadsheet

heystack_edit_spreadsheet
Destructive

Edit your Markdown Spreadsheet. Requires MCP 2026-07-28.

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": "heystack_edit_spreadsheet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the agent knows this mutates state unsafely. The description adds nothing about what is destroyed, whether prior cell/table content is overwritten, whether the edit is reversible, or what permissions are needed — all of which matter more given destructiveHint=true.

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

Conciseness3/5

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

Two short sentences with no padding, and the purpose is front-loaded. However, the second sentence is a runtime version note that occupies half the description without helping an agent decide or act.

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?

With zero parameters and no output schema, the definition is short but the remaining critical gap — a destructive edit tool that never says what content it receives or how the target spreadsheet is identified — is only partially material given the empty schema and the annotations carrying the safety profile.

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?

The tool exposes zero declared parameters and schema coverage is 100%, so per the baseline there is nothing for the description to disambiguate at the parameter level. It neither contradicts nor enriches the empty schema.

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

Purpose3/5

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

"Edit your Markdown Spreadsheet" names a verb and a resource, but the resource (a Markdown-based spreadsheet) is left undefined and no distinction is drawn from the sibling heystack_edit_markdown or heystack_create_spreadsheet. An agent cannot tell from the text what part of the spreadsheet is editable or how it differs from the plain Markdown editor.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The only conditional sentence is a version requirement ("Requires MCP 2026-07-28"), which is an environment gate rather than usage guidance for choosing this tool over heystack_edit_markdown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources