Skip to main content
Glama
sipyourdrink-ltd

Bernstein - Multi-agent orchestration

bernstein_run

Launch a multi-agent orchestration run by posting a task with a goal, role, priority, and other parameters. Get back the task ID, title, and status.

Instructions

Start an orchestration run by posting a task to the Bernstein server.

    Args:
        goal: Description of what you want Bernstein to accomplish.
        role: Specialist role to assign (backend, frontend, qa, security, …).
        priority: 1=critical, 2=normal, 3=nice-to-have.
        scope: Task scope — small, medium, or large.
        complexity: Task complexity — low, medium, or high.
        estimated_minutes: Rough time estimate in minutes.

    Returns:
        JSON with the created task ID, title, and status.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYes
roleNobackend
priorityNo
scopeNomedium
complexityNomedium
estimated_minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the action ('posting a task') and the return format (JSON with task ID, title, status). However, it does not mention permissions, side effects, or whether the operation is destructive. It is adequate but not thorough.

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?

The description is structured as a docstring with sections, but it is slightly verbose. It efficiently conveys the purpose and parameters without excess. Minor improvements could make it more compact.

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

Completeness4/5

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

Given the tool's simplicity (creation with 6 parameters, 1 required) and the presence of an output schema, the description adequately covers the return format and purpose. It is complete for an agent to understand how to use it.

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?

The input schema has 0% coverage (no descriptions in schema), so the description compensates well. It explains each parameter, including enumerated values for priority, scope, and complexity, and provides a default role. This adds significant meaning beyond the bare schema.

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 ('start an orchestration run') and the resource ('Bernstein server'), using a specific verb. It distinguishes this tool from siblings like bernstein_approve or bernstein_stop, which have different purposes.

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 only explains what the tool does but provides no guidance on when to use it versus siblings like bernstein_cost or bernstein_scenario. There is no mention of prerequisites, alternatives, or when not to use 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/sipyourdrink-ltd/bernstein'

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