Skip to main content
Glama

ovo_set_policy

DestructiveIdempotent

Configures Russell→PAD dominance and closed-loop control policies, including arousal setpoint, step limits, and consent protocol reference to arm the loop.

Instructions

Configure the Russell→PAD dominance policy and the closed-loop control policy.

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

Input Schema

NameRequiredDescriptionDefault
controlEnabledNo
arousalSetpointNo
dominancePolicyNo
maxStepPerCycleNo
protocolReferenceNoConsent / ethics protocol reference. Required to arm the control loop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say what existing policy is overwritten, that setting protocolReference arms the loop, or what the destructive side effect is. Given the destructive flag, this is a meaningful gap.

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 tight sentence with no waste, and the resource being configured is front-loaded. It is appropriately sized; the problem is omission rather than padding.

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 5-parameter, destructive, non-read-only config tool with no output schema and 20% schema coverage, this description is far too thin. It omits the effect of each setting, what gets overwritten, and when to prefer it over the related control/parameter tools.

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 20% (just protocolReference), so the description must compensate and does not. It never explains the dominancePolicy enum values (prior, endogenous, withhold), the arousalSetpoint range, or maxStepPerCycle semantics, leaving four of five parameters undocumented in both places.

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 ("Configure") and two named resources (the Russell→PAD dominance policy and the closed-loop control policy), so an agent can identify it as a policy-write tool. It is distinguishable from read/status siblings (ovo_status, ovo_read), but it does not differentiate from overlapping config siblings such as ovo_arm_control or set_parameter, and the "Russell→PAD" jargon is unexplained.

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 or when-not-to-use guidance and no mention of alternatives, despite clear overlap with ovo_arm_control (which also concerns the control loop) and set_parameter. The agent gets no signal about which tool to select for policy setup versus arming versus generic parameter writes.

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