Skip to main content
Glama

openbot_status

Read-onlyIdempotent

Check the current OpenBot connection to verify the active profile, available agents, and the T3 thread where tagged reports are delivered.

Instructions

Check the connection: the OpenBot profile in use, its agents, and the T3 thread reports go to.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openbot_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description's genuine addition is naming the returned information (active profile, agent set, where T3 thread reports are sent), which matters because there is no output schema; it says nothing about failure behavior when disconnected or what an empty/error state looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, short sentence with the action front-loaded, so it wastes no space. However, the trailing clause 'the T3 thread reports go to' is grammatically garbled and reads as a fragment, which slightly muddies otherwise compact phrasing.

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?

With no output schema and no parameters, the description is the sole source of what comes back, and it lists three payload items but not their shape, ordering, or error behavior. For a low-complexity status tool this is adequate-but-thin rather than complete.

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 tool takes no parameters, which is the baseline-4 case; the description does not need to explain any argument semantics. Nothing in the text misrepresents the parameterless nature of the call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Check' plus 'the connection' is vague about whether this is a health probe or a config/state readout; it's the enumerated payload (profile in use, its agents, T3 thread report destination) that actually tells an agent what the tool returns. It is distinguishable from siblings like list_agents because it reports connection-level context rather than performing an action, but the opening phrase alone would not get there.

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?

There is no when-to-use guidance: nothing says whether to call this before send_message/run_routine, whether it's safe to call repeatedly, or what its role is versus list_agents. For a zero-parameter status tool the usage is partially implied, but the definition leaves it entirely to inference.

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