Skip to main content
Glama
Sign In
claude-agent-bridge

claude-agent-bridge

by pinkpanther7929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

claude_set_enabled

Enable or disable bounded Claude delegation so Codex can use the local Claude CLI as a constrained reviewer or analysis delegate.

Instructions

Enable or disable bounded Claude delegation.

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": {
      "enabled": "<enabled>"
    },
    "name": "claude_set_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior traits. It doesn't say whether toggling requires authentication, what 'bounded' means, what effect enabling/disabling has, or how the change is confirmed. This is a significant 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, front-loaded and with no wasted words. However, it is under-specified rather than optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 0% schema coverage, and a mutation operation, the description is incomplete. It should clarify 'bounded', permissions, and effects, but does none of that.

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?

Schema coverage is 0% and the single parameter is undocumented in the schema. The description only implies the boolean nature via 'enable or disable', but adds no meaning like default state, idempotency, or side effects.

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 states a specific action (enable or disable) on a specific configuration (bounded Claude delegation), which is clearer than a tautology. It distinguishes from siblings enough, though 'bounded' is unexplained.

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?

No guidance on when to use this tool versus alternatives like claude_status or claude_ask is given. There are no conditions, prerequisites, or exclusions mentioned.

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