Skip to main content
Glama
Sign In
Bicameral

Bicameral

by thugpint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bicameral_check

After editing a step, diff the workspace against the snapshot, run verification, and get a second opinion from the reviewer model.

Instructions

After editing a step yourself: diff the workspace against the snapshot, run verification, and get the editor model's second opinion on your diff.

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": {
      "run_id": "<run_id>",
      "step_id": "<step_id>"
    },
    "name": "bicameral_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
step_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the full disclosure burden. It transparently enumerates the three actions the tool performs, which is meaningful behavioral context. It does not state whether the operation is read-only or whether verification/opinion results are persisted, a notable gap for a no-annotation 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?

A single sentence that front-loads the trigger and then lists the workflow in a compact, scannable form. There is no filler or repetition of schema titles. It earns a high score for efficiency.

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

Completeness3/5

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

The tool has an output schema, so the return value need not be spelled out, and the description conveys the main workflow. But it omits parameter semantics and any prerequisites/error conditions (e.g., whether a snapshot must exist), and the many bicameral siblings create ambiguity that is not resolved. Overall adequate but not complete.

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 description coverage is 0% and the description never maps run_id or step_id to roles beyond an implicit 'step'. With no parameter documentation, an agent must infer that step_id is the edited step and run_id identifies the run, which is risky. The description mentions 'a step' but does not compensate for the schema's empty parameter descriptions.

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 concrete trigger and names three specific operations (diff, run verification, second opinion), so an agent knows what invoking it accomplishes. It does not explicitly contrast with overlapping siblings such as bicameral_review_diff or bicameral_critique, so it misses the sibling differentiation that would earn 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger 'After editing a step yourself' is an explicit usage context and distinguishes this from tools used at other workflow phases. However, it gives no exclusions or mention of alternate sibling tools, so it falls short of a full 5.

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