Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blockers_resolve

Cancel or manually resolve a blocker by specifying its ID and the action (cancel or resolve) to clear dependency blockers in code tracking.

Instructions

Cancel or manually resolve a blocker.

Args:

  • blocker_id: The blocker row ID

  • action: 'cancel' (any trigger type) or 'resolve' (manual triggers only)

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": {
      "blocker_id": "<blocker_id>",
      "action": "<action>"
    },
    "name": "blockers_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
blocker_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does explain the two allowed actions and the manual-trigger restriction for 'resolve', but it does not disclose side effects, reversibility, permissions, or the post-condition state of the blocker. This is a moderate disclosure gap for a mutation tool.

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 short, front-loaded with the main purpose, and uses a compact bulleted argument list. Every sentence contributes semantic value without redundant repetition.

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?

For a two-parameter tool with an output schema present, the description provides enough information to invoke it correctly, including both parameter meanings and the conditional action rules. It stops short of full completeness due to the lack of behavioral side-effect disclosure, but nothing critical to basic invocation is missing.

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?

Schema coverage is 0%, so the description must fully compensate. It defines blocker_id as 'the blocker row ID' and enumerates the exact allowed action values with their applicability conditions, adding meaning well beyond the raw schema fields.

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 cancels or manually resolves a blocker, using specific verbs and a defined resource. It is distinct from the sibling tools like blockers_add, blockers_query, and blockers_check by expressing its resolution/cancellation purpose directly.

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?

The description provides actionable usage constraints: 'cancel' works with any trigger type, while 'resolve' is limited to manual triggers. It does not explicitly contrast with related blockers_* tools, but the action-level guidance is clear enough for correct invocation.

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