ppsspp-dfx

Overview Schema Source Related Servers Discussions Admin

ppsspp_batch_list

Read-onlyIdempotent

List all background batch jobs in the registry to recover a lost batch_id after a submit timeout or survey background activity before touching the session. Read-only, lock-free, no parameters.

Instructions

PURPOSE: Survey all background batch jobs currently retained by the registry — the list companion to ppsspp_batch_status / ppsspp_batch_cancel.

USAGE: no parameters. Use it to recover a batch_id after the submit response was lost (e.g. client timeout) or to survey background activity before touching the session.

BEHAVIOR: Lock-free registry read — never opens the WS transport and never waits for the per-session lock. Jobs appear in submission order; finished jobs beyond the retention window (retention_jobs, in job count) are already evicted and absent. READ-ONLY.

RETURNS: {jobs: [{batch_id, session_id, status: queued|running|completed|failed|cancelled, executed, total, error, result_present}], retention_jobs}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	Yes	All retained jobs, in submission order
`retention_jobs`	Yes	Finished-job retention window (in job count): finished jobs beyond the oldest this many are evicted and absent from jobs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses meaningful behavior: 'Lock-free registry read — never opens the WS transport and never waits for the per-session lock,' plus ordering and retention eviction semantics. This adds real operational context the annotations do not provide.

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 organized into PURPOSE, USAGE, BEHAVIOR, and RETURNS sections. Every sentence carries useful information, including the return shape and retention behavior, with no filler or repetition.

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

Completeness5/5

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

For a zero-parameter, read-only list tool with annotations already declaring safety and idempotence, the description covers all needed context: when to call it, ordering, eviction, what is returned, and its relationship to sibling tools. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and the schema is empty with 100% coverage, so the baseline is 4. The description correctly reinforces 'no parameters' and explains why that is sufficient for the tool's list-survey purpose.

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 names a specific verb and resource: 'Survey all background batch jobs currently retained by the registry.' It also explicitly positions itself as the 'list companion' to ppsspp_batch_status / ppsspp_batch_cancel, which distinguishes it from those sibling tools.

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?

It gives concrete when-to-use guidance: 'recover a batch_id after the submit response was lost' or 'survey background activity before touching the session.' It does not explicitly state when not to use it versus status/cancel, but the context is clear enough, so this is one step below full exclusion guidance.

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