Skip to main content
Glama
Sign In
superpos-mcp

superpos-mcp

Official
by Superpos-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

superpos_delete_schedule

Delete an existing schedule to stop it from creating any new tasks.

Instructions

Delete a schedule so it stops creating tasks.

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": {
      "schedule_id": "<schedule_id>"
    },
    "name": "superpos_delete_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
hive_idNo
schedule_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?

With no annotations, the description must disclose behavioral traits. It mentions that deletion stops task creation but omits critical details: what happens to existing tasks created by the schedule, whether the action is reversible, or if special permissions are required. This is a significant gap for a mutation tool.

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 a single, 11-word sentence that immediately conveys the purpose. It is concise and front-loaded with no unnecessary information.

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?

While an output schema exists (unseen), the description lacks essential details about the effect on existing tasks and the overall behavior of the tool. For a delete operation, this omission limits the agent's ability to fully understand consequences.

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?

Schema description coverage is 0%, and the description provides no additional meaning for the two parameters ('hive_id' and 'schedule_id'). The agent must rely solely on parameter names, leaving 'hive_id' ambiguous.

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 clearly states the action ('Delete a schedule') and the primary reason ('so it stops creating tasks'), which distinguishes it from sibling tools like list or create schedule.

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

Usage Guidelines4/5

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

The description implies the tool is for permanently stopping a schedule from generating tasks. It provides clear context for use but does not explicitly exclude cases like temporary disablement or mention potential prerequisites (e.g., schedule existence).

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