Skip to main content
Glama

Ultrabrain Status

ultrabrain_status
Read-onlyIdempotent

Get session status, thought count, branches, and latest quality score to monitor reasoning progress.

Instructions

Return session status, thought count, branches, and latest quality score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoOptional reasoning session id. Defaults to "default".
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety and idempotency. The description adds value by specifying the exact return fields (thought count, branches, quality score), which is beyond what annotations provide. No contradictions.

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?

The description is a single concise sentence with no superfluous words. It is front-loaded and efficiently communicates the tool's purpose.

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?

Lacking an output schema, the description should elaborate on the return structure or format. It lists fields but does not specify whether they are separate top-level keys or part of an object. Also, it omits error scenarios or behavior when the session_id is invalid. Adequate but incomplete.

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 description coverage is 100% for the single parameter (session_id) with its default value. The description does not add any additional meaning beyond what the schema already states, so baseline 3 is appropriate.

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 clearly states the action ('Return') and the resource ('session status'), and enumerates specific fields (thought count, branches, quality score). It distinguishes this tool from siblings like ultrabrain_analyze and ultrabrain_metrics.

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 this tool versus alternatives, or any context about prerequisites or limitations. It does not mention typical use cases or when to avoid it.

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