checkyourself

Overview Schema Source Related Servers Discussions Admin

Next Approval Batch

next

Read-onlyIdempotent

Get the next highest-severity unresolved findings for approval using backlog ranking rules. Returns up to three findings per batch to plan fixes before launch.

Instructions

Return the next highest-severity unresolved approval batch from inline findings by reusing the backlog ranking rules. The batch contains at most the first three unresolved findings at the highest current severity; safety and dependency analysis are not performed. This is a planning tool only and does not perform fixes. Requires no authentication. It reads local inputs only, does not make network calls, does not modify local files, and has no external rate limits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`findings`	Yes	Scan result object, CheckYourself report object, object with findings/remediation_backlog, or a plain list of finding objects to batch into the next approval group.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.2Sep 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / findings / description

Added value: +"Scan result object, CheckYourself report object, object with findings/remediation_backlog, or a plain list of finding objects to batch into the next approval group."

changedInput schema / properties / findings / type

Previous value: -"object"New value: +[
+  "object",
+  "array"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Next-batch result using schema checkyourself-next-batch/1.",
+  "type": "object"
+}

First observedv0.1.0Jun 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description is highly transparent: no authentication, reads local inputs only, no network calls, no file modifications, no external rate limits, and idempotent/read-only behavior. This aligns with the annotations and leaves nothing hidden.

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 compact yet comprehensive, covering purpose, constraints, and side effects in two sentences. It is well-structured and every sentence adds meaningful information.

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?

Given the tool's simplicity (one parameter, no destructive actions), the description fully covers all relevant aspects: purpose, input, behavior, limitations, and side-effect-free guarantees. Nothing is missing for correct invocation and understanding.

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?

The schema already provides a detailed description of the 'findings' parameter covering multiple accepted forms. The tool description adds minimal extra context ('to batch into the next approval group'), so with 100% schema coverage, a baseline score of 3 is appropriate.

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 tool returns the next highest-severity unresolved approval batch from inline findings using backlog ranking rules. It specifies the verb 'Return' and the resource 'approval batch', and distinguishes itself as a planning-only tool.

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 explicitly says this is a planning tool only and does not perform fixes, which gives clear usage guidance. It does not name sibling alternatives directly, but the context of planning vs. fixing is communicated effectively.

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

Deploy Server