Skip to main content
Glama

ovo_isomorphism

Read-onlyIdempotent

Compare silicon SNN, organoid MEA, and human wearable substrates in one PAD pipeline to see which axes each constrains and the caveat that blocks naive isomorphism claims.

Instructions

Side-by-side comparison of the three substrates feeding the same PAD pipeline (silicon SNN, organoid MEA, human wearable), with the axes each can constrain and the caveat that blocks a naive isomorphism claim.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered. The description adds useful content framing (three substrates, the axes each constrains, the caveat blocking naive isomorphism) but says nothing about output form, cost, or determinism beyond what annotations imply.

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 with the comparison subject front-loaded and no filler. It is appropriately sized, though the trailing 'caveat that blocks a naive isomorphism claim' phrase is slightly abstract and could be more concrete.

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?

For a zero-argument read tool with no output schema, the description should carry the burden of describing the returned structure, and it only gestures at it ('axes each can constrain', 'caveat'). It is enough to know what the tool is about, but not enough to anticipate the shape of the result.

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 per the rubric the baseline is 4. The description legitimately clarifies what the parameterless call compares rather than leaving the agent guessing, though it adds no argument semantics to disambiguate.

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 names a concrete action (side-by-side comparison) and a concrete resource scope (the three substrates feeding the same PAD pipeline), so an agent knows exactly what it returns conceptually. It does not, however, explicitly contrast itself against the many sibling orchestration tools (orch_substrate, ovo_read, ovo_status), so differentiation is left to inference.

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?

Usage is only implied: an agent can guess this is the tool to call when evaluating an isomorphism claim across substrates, but there is no explicit 'use this when...' or 'do not use instead of ovo_read/ovo_status' guidance. With dozens of ovo_/orch_ siblings, an explicit routing sentence would materially help.

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