codebugs

Overview Schema Source Related Servers Discussions Admin

pull_next

Claim the next eligible code finding, release, triage, or maintenance item based on priority and agent capacity. Returns the item dict, or None if nothing is eligible.

Instructions

Claim the next eligible item for the calling agent. Returns the item dict or None if nothing eligible.

Priority: stream/security > release/* (earliest target_date) > stream/triage > stream/maintenance.

Args:

agent_id: Stable id for the calling agent. Used as actor in audit.
capacity: Dict like {'large':1,'small':2,'triage':5}. Defaults to those values if not provided.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "pull_next"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes
`capacity`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Aug 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations to fall back on, the description discloses key behavior: it returns the item dict or None, applies a priority order, and uses agent_id as the audit actor. It also reveals capacity defaults. It does not explicitly state that claiming is a persistent state change, though 'Claim' implies mutation.

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 compact and front-loaded with the action and return value; the priority block and args are clearly separated. The priority syntax is slightly dense but not wasteful.

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?

The description covers purpose, return behavior, selection priority, and both parameters. It does not define 'eligible' in detail or explain how capacity interacts with eligibility, but the provided info is sufficient for basic invocation, especially with an output schema present.

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

Parameters5/5

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

The schema only provides names and types; the description supplies essential semantics: agent_id is a stable id used as actor in audit, and capacity is a dict with example keys and default values. This fully compensates for the 0% schema description coverage.

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 opens with a specific verb and object: 'Claim the next eligible item for the calling agent,' and states the return type. It conveys the tool's role in a queue, but it does not explicitly differentiate from sibling claim tools like claims_claim or codesweep_next, so it stops short of a 5.

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?

The description explains how the tool selects items via a priority order but gives no guidance on when to choose pull_next over sibling tools such as claims_claim or codesweep_next. There are no explicit when-to-use or when-not-to-use instructions, and no alternative tool is mentioned.

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

Deploy Server