Skip to main content
Glama

Submit a signed contribution

heystack_submit_contribution
Destructive

Submit a signed contribution. 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_submit_contribution"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 covered and the description is not contradictory. However, the description adds almost nothing beyond that: it never says what a submission destroys or overwrites, whether it is reversible, or what signing means in practice — significant gaps for a destructive tool.

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 short sentences, front-loaded with the action, and no padding or repetition of the title. The second sentence is terse to the point of being cryptic, but nothing is wasted.

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 destructive, non-idempotent, zero-parameter tool with no output schema, an agent needs to know what a contribution is, how the content reaches the server, and what the side effects are. None of that is covered, so the definition is incomplete relative to its risk profile.

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

Parameters3/5

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

With zero parameters the baseline is 4, but the description squanders it: it never explains how the contribution payload is supplied when the schema accepts no arguments at all. That omission leaves the calling convention genuinely ambiguous, so it falls below the empty-schema baseline.

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?

The description gives a verb and an object ("Submit a signed contribution"), which is better than a bare title restatement, but "contribution" is left undefined — the agent cannot tell whether this is a document edit, a suggestion, or a moderation artifact. Nothing in the text differentiates it from siblings such as heystack_suggest_edit or heystack_review_suggestion.

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?

"Requires MCP 2026-07-28" is a precondition, not usage guidance; it does not say when to submit versus use suggest_edit or comment. There is no statement of when NOT to use it, no alternatives, and no indication of what a signed contribution is in this system.

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