Skip to main content
Glama

Suggest an edit

heystack_suggest_edit

Suggest an edit. 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_suggest_edit"
  }
}

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 safety profile is covered. The description adds one genuine piece of context, the MCP 2026-07-28 requirement, but says nothing about what a suggestion does, whether it notifies reviewers, or how it is later approved.

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, so it is not verbose. However, its brevity comes from under-specification rather than economy, and the version requirement is placed ahead of any explanation of what the tool does.

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 non-read-only mutation tool with no parameters and no output schema, the description should at minimum explain what the suggestion targets and what happens to it. It leaves that implicit context entirely unstated and never distinguishes itself from the nearby edit and contribution tools.

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 empty, so there is no parameter semantics to compensate for; the baseline applies. The description adds nothing here, but nothing is needed.

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?

"Suggest an edit" merely restates the tool name and title; it never says what resource is being edited (markdown document, spreadsheet, topic) or what a suggestion contains. Siblings like heystack_edit_markdown and heystack_submit_contribution are indistinguishable from it on the description alone.

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 and no mention of alternatives such as heystack_edit_markdown or heystack_submit_contribution, which likely overlap. The only constraint offered, the MCP version gate, is a compatibility prerequisite rather than usage guidance.

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