Skip to main content
Glama

Ultrabrain Reset

ultrabrain_reset
DestructiveIdempotent

Reset a reasoning session to its initial state, or clear all sessions to start fresh.

Instructions

Reset one Ultrabrain session, or all sessions when all_sessions is true.

Input Schema

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

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

Annotations already indicate destructiveHint: true and idempotentHint: true. The description only says 'reset,' but does not explain what resetting entails (e.g., clearing reasoning state, deleting history). It adds minimal behavioral context beyond what annotations provide.

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, well-structured sentence that conveys the core functionality and key parameter interaction. No wasted words, and the behavior is front-loaded.

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 is simple with two optional parameters and no output schema. The description and schema together cover the basic usage, but lack explanation of what 'reset' means operationally (e.g., side effects). Given the destructive annotation, more detail would improve completeness.

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 50% (only session_id has description). The description adds that all_sessions triggers reset of all sessions and clarifies session_id defaults to 'default.' This adds some value but does not fully compensate for the missing parameter documentation.

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 tool resets 'one Ultrabrain session, or all sessions when all_sessions is true.' It specifies the verb 'reset' and the resource 'Ultrabrain session,' and distinguishes between single and bulk reset, differentiating it from sibling tools like start, update, etc.

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 like ultrabrain_start or ultrabrain_analyze. There is no mention of prerequisites, context switches, or when not to use it, leaving the agent without decision support.

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