Skip to main content
Glama
Sign In
codex-claude-bridge-mcp

codex-claude-bridge-mcp

by nevzoom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

claim_task

Claim an open task to reserve it for a specific owner (Codex, Claude, or human) before beginning work, preventing duplicate ownership.

Instructions

Claim an open task before starting work; prevents duplicate ownership.

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": {
      "task_id": "<task_id>",
      "owner": "<owner>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait—'prevents duplicate ownership'—which implies a conflict mechanism and side effect. However, it does not detail what happens on failure or other transactional details.

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 a single concise sentence of 10 words that front-loads the action and purpose. Every word earns its place with no redundancy.

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 simple claim operation with two parameters and no output schema, the description covers purpose, usage, and a key behavioral guarantee. It lacks explicit parameter explanations, but the enum on owner and the task description partially compensate. Overall, it is sufficiently complete for basic selection and invocation.

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

Parameters2/5

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

The schema description coverage is 0%, and the description does not explain the 'task_id' or 'owner' parameters at all. The agent must infer their meaning from the parameter names and the owner enum, so the description adds no semantic value beyond the schema.

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's function with a specific verb and resource: 'Claim an open task before starting work; prevents duplicate ownership.' This also distinguishes it from sibling tools like create_task or update_task by emphasizing the ownership/claiming aspect.

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 gives clear context for when to use the tool: 'before starting work' on a task. It does not explicitly name alternatives or exclusions, but the workflow context is clear enough for selecting this tool over others.

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