Skip to main content
Glama
Sign In
superpos-mcp

superpos-mcp

Official
by Superpos-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

superpos_close_issue

Closes an issue as done, allowing an optional closure reason, and respects the issue type's closure policy.

Instructions

Close an issue as done, optionally recording a closure reason. Subject to the issue type's closure policy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_id": "<issue_id>"
    },
    "name": "superpos_close_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
hive_idNo
issue_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the action is subject to a closure policy, but omits details on side effects (e.g., notifications, state changes), permissions, or whether the action is reversible.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary action, and no redundant information. Every sentence is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and partial parameter coverage, the description is minimally adequate. It mentions the closure policy but does not explain what that entails, and the output schema is present but unaddressed.

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 0% schema description coverage, the description adds value for the 'reason' parameter by stating it is optional, but it does not mention the 'hive_id' parameter or clarify its purpose, leaving gaps.

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

Purpose5/5

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

The description uses a specific verb ('Close') and resource ('issue'), and clarifies the state ('as done') with optional reason recording, clearly distinguishing from sibling tools like superpos_transition_issue.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for final closure of an issue, but does not explicitly state when to use this vs. alternative tools like superpos_transition_issue for other transitions, nor does it provide exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools