Skip to main content
Glama

Ultrabrain Branch

ultrabrain_branch

Create or continue a reasoning branch from a prior thought to explore alternative paths or revise conclusions.

Instructions

Create or continue an Ultrabrain branch from a prior thought.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoOptional reasoning session id. Defaults to "default".
response_formatNoResponse format.
thoughtYesCurrent Ultrabrain reasoning step.
thought_numberYesCurrent thought number in the chain.
total_thoughtsYesEstimated total thoughts. Adjust this as scope changes.
next_thought_neededYesSet to false only when this chain has reached a verified conclusion.
step_typeNoReasoning step category.
modeNoReasoning mode.
is_revisionNoWhether this step revises an earlier thought.
revises_thoughtNoThought number being revised.
branch_from_thoughtYesThought number where this branch starts.
branch_idYesBranch identifier.
parent_thoughtNoOptional parent thought reference.
needs_more_thoughtsNoAllows thought_number to exceed total_thoughts when scope expands.
depth_levelNoCurrent depth for serial reasoning.
max_depthNoMaximum planned depth.
budget_modeNoReasoning budget mode.
budget_usedNoBudget used percentage from 0 to 100.
confidenceNoConfidence from 0 to 1.
meta_checkpointNoMarks an explicit meta-reasoning checkpoint.
bias_detectedNoKnown cognitive bias to track.
quality_metricsNoQuality scores from 0 to 5.
evidenceNoEvidence supporting this thought.
assumptionsNoAssumptions to track.
open_questionsNoUnresolved questions.
alternativesNoAlternative paths or options.
risksNoKnown risks.
next_actionsNoConcrete next checks or implementation actions.
tagsNoOptional tags.
perspectiveNoOptional perspective, such as reviewer, maintainer, security, UX, or operator.
expected_outputNoExpected output from the reasoning chain.
hypothesisNoExplicit hypothesis for this step.
verificationNoVerification approach or result.
Behavior3/5

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds minimal context beyond that; it does not elaborate on side effects or behavioral nuances.

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?

Single, clear sentence. Efficient but lacks structuring like bullet points for key info; still good for a simple description.

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?

Tool has 33 parameters, nested objects, and no output schema. Description is minimal; does not explain return values or operational impact, leaving significant gaps for a complex tool.

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

Parameters3/5

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

Schema coverage is 100%, so descriptions already explain parameters. The tool description adds no extra semantic value beyond what the schema provides.

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 'Create or continue an Ultrabrain branch from a prior thought' uses specific verbs and a clear resource, and distinguishes from sibling tools like ultrabrain_start and ultrabrain_think.

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 vs alternatives (e.g., ultrabrain_think or ultrabrain_start), nor any conditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LCV-Ideas-Software/ultrabrain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server