Skip to main content
Glama
Sign In
codebugs

codebugs

by faxik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

codemerge_sessions

List merge sessions with claim counts to track code merge progress. Filter by status: active, merging, done, or abandoned.

Instructions

List merge sessions with claim counts.

Args:

  • status: Filter by status ('active', 'merging', 'done', 'abandoned'). Omit for all sessions.

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

Input Schema

NameRequiredDescriptionDefault
statusNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/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 states that the tool lists sessions and includes claim counts, which implies a read-only operation, but it does not explicitly confirm no side effects, pagination behavior, or ordering. It is adequate but not rich.

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 brief, front-loaded with the primary purpose, and every sentence adds value. The parameter documentation is compact and directly actionable, with no filler.

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 tool is simple: one optional parameter, no required fields, and an output schema exists to define return values. The description covers the parameter semantics and core behavior well. It is only missing when-to-use guidance relative to the many codemerge siblings.

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 description coverage is 0%, so the description must compensate. It fully does: it lists the four allowed status values ('active', 'merging', 'done', 'abandoned') and clarifies that omitting the parameter returns all sessions. This goes beyond the schema's vague nullable string.

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 uses a specific verb and resource: 'List merge sessions with claim counts.' This clearly identifies the operation and one key output detail. However, it does not explicitly differentiate itself from related siblings like codemerge_status or codemerge_claims, 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 to filter by status but gives no guidance on when to choose this tool over alternatives. Sibling tools such as codemerge_status and codemerge_claims exist, yet no exclusions or selection criteria are provided.

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