Skip to main content
Glama

ovo_read

Read-only

Poll one OVOMIND affect frame into PAD, returning each axis with epistemic tier, provenance, and basis string; dominance is never estimated from the human channel.

Instructions

Poll one OVOMIND affect frame and lift it into PAD. Every axis is returned with its epistemic tier, provenance and basis string. Dominance is never estimated from the human channel.

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

Input Schema

NameRequiredDescriptionDefault
controllabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond that: every axis is returned with epistemic tier, provenance and basis string, and dominance is never inferred from the human channel. It still does not explain what 'PAD' or an 'epistemic tier' is, nor the polling cadence for a non-idempotent read.

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?

Three short sentences with the action front-loaded, no filler. The final sentence on dominance is terse and slightly cryptic, but each sentence contributes information.

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, the description does some of the load-bearing work by describing the returned fields, and annotations cover safety. However, key domain terms (PAD, epistemic tier, dominance vs human channel) are undefined and the lone input parameter is unexplained, so an agent can select the tool but cannot fully reason about its contract.

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

Parameters1/5

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

Schema description coverage is 0% and the single parameter 'controllability' (a 0-1 number) is never referenced in the description. With a non-zero parameter count and no schema descriptions, the description carries the burden and adds nothing, leaving the parameter's meaning and units unknown.

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 and resource: 'Poll one OVOMIND affect frame and lift it into PAD', and adds what the result contains (each axis with epistemic tier, provenance and basis string). It is clear what the tool does, though it never names a sibling (ovo_status, ovo_cycle, ovo_isomorphism) to disambiguate it within the crowded OVO family.

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?

'Poll' implies retrieving a current frame, but there is no explicit when-to-use, no preconditions, and no mention of the sibling tools such as ovo_status or ovo_cycle that an agent would otherwise consider. The agent is left to infer selection entirely.

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