Skip to main content
Glama

ovo_status

Read-onlyIdempotent

Check OVOMIND bridge state to see adapter mode, substrate descriptor, frame counters, and synthetic-phenomenology ethics assessment for the current configuration.

Instructions

OVOMIND bridge status: adapter mode, substrate descriptor, frame counters, and the synthetic-phenomenology ethics assessment for the current configuration.

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": "ovo_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds meaningful value by enumerating what the status actually surfaces, notably the synthetic-phenomenology ethics assessment, which is not derivable from any structured field.

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?

A single dense sentence that front-loads the resource ('OVOMIND bridge status') and then lists its components. No filler, though the long enumerated payload makes it slightly list-heavy rather than crisp.

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?

With no input parameters and no output schema, the description is the only source of return-value information, and it names the key components including the ethics assessment. It is nearly complete for a status tool, missing only how/when it should be invoked or refreshed.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not need to explain inputs and correctly focuses on outputs instead.

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

Purpose4/5

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

States a specific verb+resource: it reports the OVOMIND bridge status, and enumerates the concrete contents (adapter mode, substrate descriptor, frame counters, ethics assessment). This clearly separates it from read/write siblings such as ovo_cycle or ovo_set_policy, though it never explicitly contrasts itself with lookalikes like get_system_status or ovo_isomorphism.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling status/telemetry tools (get_system_status, get_metrics, np_status). The agent must infer timing and context entirely on its own.

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