Skip to main content
Glama

Accept or reject a suggestion

heystack_review_suggestion
Destructive

Accept or reject a suggestion. 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_review_suggestion"
  }
}

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 destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The only added behavioral context is the MCP version requirement; the description does not say what gets destroyed on rejection, whether it is reversible, whether acceptance publishes content, or what permissions are needed. For a destructive, non-idempotent operation this leaves significant gaps.

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

Conciseness4/5

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

Two brief sentences with the action front-loaded and the prerequisite last; nothing is padded. The brevity borders on under-specification rather than verbosity, but structurally it is clean.

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?

This is a destructive, irreversible-sounding moderation action with no output schema and no parameters. Given that complexity, the description should explain the target selection, the effect of each choice, and the response, none of which are present.

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

Parameters2/5

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

The schema has zero parameters, yet the description describes a binary decision and an implicit target suggestion. Nothing explains how the suggestion identity or the accept/reject choice is supplied, which makes the described capability look unsupported by the input schema. The empty schema baseline does not help here because the description raises questions the schema cannot answer.

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

Purpose4/5

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

The description names a specific verb pair and resource: 'Accept or reject a suggestion.' An agent can tell it acts on suggestions and involves a binary moderation decision. It stops short of tying itself to any sibling (e.g. heystack_read_moderation or heystack_suggest_edit), so differentiation is left to the reader.

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 guidance on when this tool should be chosen over reading moderation queues or suggesting an edit, and no prerequisites or exclusions are stated. It only states a technical requirement ('Requires MCP 2026-07-28'), which is a compatibility note, not 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