Skip to main content
Glama

maestro_abort

Cancel an active MAESTRO interview and immediately free up resources.

Instructions

Abort and cleanup a MAESTRO session.

Use this to cancel an in-progress interview and free resources. Sessions automatically expire after 1 hour, but you can use this to immediately cleanup if needed.

Args: session_id: Session ID to abort

Returns: Dict containing: - success: True if session was aborted, False if not found - message: Human-readable status message

Example: # Abort an active session result = await maestro_abort(session_id="maestro_abc123") if result["success"]: print("Session aborted successfully")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
Behavior4/5

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

No annotations provided; description discloses the tool aborts sessions, returns a dict with success and message, and that sessions auto-expire. Could mention more about side effects, but sufficient for a simple operation.

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?

Well-structured with Args, Returns, and Example sections. Slightly verbose but clear and front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, parameter, return value, and example thoroughly for a simple tool. No gaps given the tool's complexity.

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?

Schema coverage is 0%, so description compensates by defining 'session_id: Session ID to abort' and showing usage in an example. Adds value beyond schema's minimal title.

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 states 'Abort and cleanup a MAESTRO session' with a specific verb and resource, clearly distinguishing it from sibling tools like 'maestro_start_session' or 'maestro_answer'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use for canceling an in-progress interview and freeing resources, and mentions automatic expiration after 1 hour. Lacks explicit exclusions or alternatives, but context is clear.

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/archolet/claude-gemini-bridge'

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