Skip to main content
Glama

Create a Markdown Document

heystack_create_markdown

Create a Markdown Document. 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_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation and safety profile is covered structurally. The description adds nothing beyond an opaque "Requires MCP 2026-07-28" clause — it doesn't say where the document is created, what initial content it gets, or whether creation is idempotent or error-prone. Notably, with zero parameters it is unclear what document is even being created.

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?

It is short and front-loaded, but that is brevity through omission rather than efficiency — the second sentence is cryptic and the first is pure duplication. Two sentences that convey almost no operational information does not count as well-structured.

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/mutation tool with no output schema, no parameters, and a sibling editor tool, the description is far too thin: an agent cannot tell what a created markdown document contains, where it lives, or how this differs from editing. Annotation coverage of the mutation profile is the only thing making it callable.

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 and the schema is an empty object, so there is no parameter semantics to explain; a baseline of 4 applies. The description neither helps nor harms here, though the absence of any content/title parameter is itself a gap the description could have addressed.

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 is a verbatim restatement of the tool name and title ("Create a Markdown Document") with no additional scope, target location, or distinguishing detail. It doesn't separate this from heystack_edit_markdown or heystack_create_spreadsheet in any way. Per the rubric, restating the name/title is tautology.

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 mention of alternatives such as heystack_edit_markdown for existing documents. The only additional sentence is a version requirement, which does not tell an agent when to select this tool over a sibling.

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