Skip to main content
Glama
Sign In
Bicameral

Bicameral

by thugpint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bicameral_stats

Get success rates, routing table, evaluation results, and top lessons from the Bicameral two-model coding workflow to assess performance and guide improvements.

Instructions

Success rates, routing table, eval results and top lessons.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 only lists content categories and does not state that the tool is read-only, mention data freshness, side effects, or access requirements. It is not contradictory, but it is behaviorally thin.

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 compact, six-word list with no filler or redundant phrasing. It is appropriately front-loaded, though its telegraphic style sacrifices some explanatory context.

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 parameterless reporting tool with an output schema present, the description gives enough orientation by listing the main content areas. It does not need to explain return values in detail, though adding a note about when to use it would improve completeness.

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

Parameters4/5

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

The tool has zero parameters and the schema description coverage is effectively 100%, so the schema already exhaustively documents the input surface. The baseline of 4 applies, and the description does not need to add parameter details.

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 clearly enumerates the tool's content: success rates, routing table, eval results, and top lessons. Although it lacks an explicit verb like 'get' or 'return', the noun phrase unambiguously identifies this as a stats/reporting tool and goes beyond simply restating the tool name.

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 provides no guidance on when to use bicameral_stats versus siblings like bicameral_status or bicameral_recall. An agent must infer usage from the tool name and content list, with no exclusions or alternative routing.

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