Skip to main content
Glama

Create a Markdown Spreadsheet

heystack_create_spreadsheet

Create a 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_create_spreadsheet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive nature is covered. The description contributes only a version requirement; it says nothing about what gets created, whether the caller receives an identifier, or how the resource is scoped (topic/document).

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 filler, so it is structurally clean. However, the brevity is under-specification rather than economy — no sentence explains what a "Markdown Spreadsheet" is or what the call produces.

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?

For a creation tool with no input schema and no output schema, the description carries the full burden of explaining inputs and results, and it does not. An agent cannot tell what the new spreadsheet is attached to, what it returns, or how to subsequently address it with edit_spreadsheet.

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 takes zero parameters, so there is no schema semantics for the description to carry; baseline is 4. Nothing in the description contradicts or misrepresents the empty parameter object.

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?

States the verb+resource ("Create a Markdown Spreadsheet"), but this is a verbatim restatement of the title, so the description adds no explanatory content beyond the name. It also gives no basis for choosing it over the sibling heystack_create_markdown or heystack_edit_spreadsheet.

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 only guidance is a version prerequisite ("Requires MCP 2026-07-28"). There is no statement of when to use this versus create_markdown or edit_spreadsheet, and no preconditions about where the resulting spreadsheet lives.

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