Skip to main content
Glama

ovo_arm_control

DestructiveIdempotent

Arm or disarm closed-loop affective actuation to place a human subject inside the control loop; arming is refused without a protocol reference.

Instructions

Arm or disarm closed-loop affective actuation. Arming places a human subject inside the control loop and is refused without a protocol reference.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "arm": "<arm>"
    },
    "name": "ovo_arm_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
armYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds genuinely new behavioral context: arming puts a human subject inside the control loop (a consequential side effect) and requires a protocol reference or the call is refused. That refusal condition is not visible in the annotations or schema.

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?

Two tight sentences, with the core operation front-loaded and the precondition following. No filler or redundant restatement of the tool name.

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?

For a single-boolean mutation tool with no output schema, the description covers the operation, its consequence, and its gating condition. The one loose end is that the stated 'protocol reference' requirement has no corresponding parameter in the schema, leaving the agent unsure how that precondition is satisfied.

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

Parameters3/5

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

There is one parameter (arm, boolean) with 0% schema description coverage, so the description's 'Arm or disarm' gives only the obvious polarity. It does not clarify the default, the effect of omitting it, or how it interacts with the protocol-reference precondition.

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?

States a specific verb pair (arm/disarm) and a specific resource (closed-loop affective actuation), which distinguishes it from the many sibling ovo_ tools like ovo_set_policy or ovo_cycle. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a precondition (arming is refused without a protocol reference) but never states when to choose this tool over alternatives such as ovo_set_policy or the closed-loop siblings. Usage context is implied rather than spelled out.

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