Skip to main content
Glama
Sign In
BitPull

BitPull

by SamuealPK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bitpull_schedule_delete

Delete a scheduled task by UUID to remove obsolete or unwanted jobs from BitPull.

Instructions

Delete a scheduled task.

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": {
      "id": "<id>"
    },
    "name": "bitpull_schedule_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

The description says the tool deletes a task, but the annotations declare destructiveHint=false. Deleting a scheduled task is inherently a destructive mutation, so the description directly conflicts with the supplied annotation. No additional context about irreversibility, confirmation, or side effects is offered.

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?

It is a single short sentence with no wasted words and the action is front-loaded. However, the brevity comes at the cost of under-specification, so it is concise without being informative.

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 delete operation with no output schema and zero schema description coverage, the definition omits critical information: which task is targeted, whether deletion can be undone, and how the call relates to schedule creation/saving. The definition is not complete enough for an agent to invoke confidently.

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% for the single 'id' parameter. The description does not state that the UUID identifies the scheduled task to delete, nor whether it must reference an existing/newly saved schedule. It adds no meaning beyond the bare schema.

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?

States a specific verb ('Delete') and resource ('scheduled task'), which is enough to distinguish it from siblings like bitpull_schedule_save and bitpull_schedule_run. It does not explicitly differentiate itself from other schedule-management tools, but the verb+resource pairing is unambiguous.

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 to use this tool versus bitpull_schedule_save or bitpull_schedule, no prerequisites, and no mention of whether deletion is permanent or reversible. The agent must infer the entire usage context from the name alone.

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