Skip to main content
Glama

ovo_cycle

Reads one affect frame and runs a TCAI cycle, treating the human channel as the body specialist and excluding human valence from rewardSignal; optionally computes a control command.

Instructions

Read one affect frame and run a TCAI cycle with the human channel entering as the body specialist. The human valence is NOT routed to rewardSignal.

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_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
actuateNoAlso compute a control command (requires an armed controller).
controllabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already disclose that this is not read-only, is open-world, non-idempotent, and non-destructive. The description adds meaningful behavioral context by specifying that the human channel enters as the body specialist and that human valence is not routed to rewardSignal, which is useful routing information beyond the annotations.

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?

The description is two tight sentences with no filler. The core action is front-loaded, and the routing exception follows immediately, so every sentence earns its place.

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

Completeness2/5

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

For a non-read-only cycle tool with no output schema, the description omits return behavior, side effects, prerequisites such as an armed controller for actuate, and usage context. Annotations cover the safety profile, but the description leaves too much unspecified for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description does not clarify the two parameters (actuate and controllability) or their effects. Since the schema already describes actuate but leaves controllability undocumented, the description fails to compensate for the coverage gap.

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?

The description states a specific compound action: read one affect frame and run a TCAI cycle, with a routing caveat about the human channel. It is clear within the OVOMIND/TCAI domain, but it does not differentiate itself from the sibling tools tcai_cycle or ovo_read, so it stops short of a 5.

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 explains what the tool does but gives no guidance on when to use it versus alternatives such as ovo_read, ovo_status, or tcai_cycle. There are no explicit when/when-not conditions or recommended contexts.

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