boinc-central-mcp

Overview Schema Source Related Servers Discussions Admin

list_batches

Read-onlyIdempotent

Lists an account's BOINC Central batches newest first, excluding retired batches, with an optional state filter for init, in_progress, complete, or aborted.

Instructions

List the account's batches (newest first). Retired batches are not returned by the server. Optional state filter: init, in_progress, complete, aborted. app_name is "buda" for BUDA (Docker) batches.

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": "list_batches"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral detail beyond that: results are newest first, retired batches are omitted by the server, and the state filter has specific accepted values. The app_name sentence is a little unclear because no such parameter appears in the schema, but it does not contradict the annotations.

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?

The description is short and front-loaded with the primary action and ordering. The final app_name sentence is slightly confusing and does not clearly map to a parameter, but overall there is little wasted text.

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?

An output schema exists, so the description need not explain return values. It covers ordering, retired-batch exclusion, and the optional state filter, leaving mainly the sibling-tool selection guidance as a gap.

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 say the state filter is optional and lists its values, but those values are already enumerated in the schema, and the description does not clarify default behavior or any other parameter semantics. The app_name mention introduces a concept not represented in the input 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?

The description states a specific verb and resource: list the account's batches, with scope (newest first) and an explicit exclusion (retired batches are not returned). It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as batch_status or batch_jobs.

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?

Usage is implied by 'List the account's batches' and the optional state filter, but there is no explicit guidance on when to use this tool versus batch_status, batch_jobs, or job_details. The agent must infer the selection conditions.

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

Deploy Server