Check which Renga–Codex Bridge features are available and distinguish planned release scope from tested local integration evidence before running modeling or export tasks.
Return release scope; research and actual local integration evidence are distinguished.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. 'Return' implies a read-only operation, and the clause stating research evidence is distinguished from actual local integration evidence does disclose something about the returned content's provenance. However, it says nothing about authentication, whether it queries the host environment, or how the two evidence classes are distinguished.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single short sentence, which is appropriately sized, and the verb 'Return' is front-loaded. But the semicolon clause is cryptic enough that roughly half the text does not clearly earn its place for an agent trying to decide whether to call it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter introspection tool with no annotations and no output schema, the description must explain what is actually returned. It never defines 'release scope', does not say what capabilities are enumerated, and gives no output shape, leaving an agent unable to predict the result of calling it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema accepts zero parameters, so there is no parameter semantics for the description to add — baseline 4 applies. The description's only parameter-adjacent information is that no scope filter is offered, which is implicit in the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description says 'Return release scope', which gives a verb but an ambiguous resource — 'release scope' is not clearly defined and the name 'bridge_capabilities' suggests something broader (system capabilities) that the text never confirms. The second clause about research vs. local integration evidence hints at scope but does not make the tool's purpose identifiable against 21 bridge_* siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to call this tool, what question it answers, or how it differs from relatives like bridge_status, bridge_project_info, or bridge_catalogs. With 21 sibling tools and no routing guidance, selection is left entirely to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.