Skip to main content
Glama
Sign In
boinc-central-mcp

boinc-central-mcp

by ispacex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

retire_batch

DestructiveIdempotent

Permanently delete a BOINC Central batch's collected output, cancel its unsent jobs, and hide it from listings. Download output first; requires explicit confirmation.

Instructions

DESTRUCTIVE: retire the batch on BOINC Central: the server immediately deletes the batch's collected output (results/<batch_id>, i.e. what download_batch_output fetches), cancels its unsent jobs and hides it from listings. Download the output first. Call only when the user explicitly asked, and pass confirm=true.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "retire_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
batch_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds exactly the detail those hints cannot convey: the deletion happens immediately on the server, it covers results/<batch_id> (the same data download_batch_output fetches), and unsent jobs are cancelled. This is genuine added behavioral context rather than restatement.

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?

Front-loaded with the DESTRUCTIVE marker, then consequences, then the operational instructions. Four compact sentences with no filler; the ordering mirrors how an agent should reason about the call.

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

Completeness4/5

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

Output schema exists, so return values need not be explained, and the destructive semantics plus prerequisites are well covered. What is missing is the relationship to abort_batch (when cancellation rather than retirement is the right call) and the failure mode when confirm is not set.

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?

Schema coverage is 0%, so the description must carry parameter meaning; it does explain that confirm must be true but not what happens if it is false/omitted, and batch_id is only implicitly characterized via the results/<batch_id> path. Partial compensation for a two-parameter schema with no descriptions.

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 and resource ('retire the batch on BOINC Central') and immediately enumerates the concrete effects: output deletion, unsent job cancellation, hiding from listings. It references download_batch_output as a related tool but never distinguishes itself from the closest sibling, abort_batch, so an agent cannot fully separate the two from the description alone.

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

Usage Guidelines5/5

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

Explicit sequencing ('Download the output first'), an explicit authorization gate ('Call only when the user explicitly asked'), and an explicit required argument value ('pass confirm=true'). That is a clear when-to-use plus prerequisite and consent policy in one place.

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