aperture-mcp

Overview Schema Source Related Servers Discussions Admin

compare

Detects when tracked commitments disappear between document versions by comparing two text states and reporting violations based on verbatim anchor presence.

Instructions

Surface drift between two text states of the SAME decision object (state_a = earlier, state_b = later). Pass anchors=[{kind, id}] to track specific constraints/goals/commitments/baselines — an id present in state_a but missing from state_b reads as violated (directional; an id absent from state_a does not trigger), and the id must appear VERBATIM (case-insensitive substring) to match — so RE-STATE tracked anchors verbatim in state_b (a constraint you kept but did not re-state still reads as violated). Returns an 8-value status (only 4 are emitted on this surface) + violations + reason. Heuristic, not a semantic judge; a drift signal, not a sole gate.

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": {
      "state_a": "<state_a>",
      "state_b": "<state_b>"
    },
    "name": "compare"
  }
}

Input Schema

Name	Required	Description	Default
`anchors`	No
`state_a`	Yes
`state_b`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: directional violation detection (only missing from state_b triggers), verbatim case-insensitive substring matching, return of 8-value status (only 4 emitted), and heuristic nature. No contradictions.

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?

The description is comprehensive but slightly verbose (5 sentences). Each sentence adds value, but some pruning (e.g., combining anchor rules) could improve conciseness while maintaining clarity.

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?

Given complexity (anchor tracking, directional violations, heuristic nature), the description covers key aspects. Output schema exists but is not shown; however, the description mentions return values sufficiently. The remaining 4 status values are not explained, but this is likely covered by output schema.

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

Parameters5/5

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

Despite 0% schema coverage, the description adds rich meaning: state_a is earlier, state_b later; anchors track specific items with detailed matching rules and violation semantics. This fully compensates for the schema's lack of parameter descriptions.

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?

The description clearly states the tool's purpose: 'Surface drift between two text states of the SAME decision object.' It distinguishes from sibling tools like compare_stance and compare_commitment by focusing on text state comparison and anchor tracking.

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

Usage Guidelines4/5

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

Provides context on when to use (detecting drift between same object) and how anchors work. Implicitly advises not to treat as sole gate via 'Heuristic, not a semantic judge; a drift signal, not a sole gate.' However, no explicit when-not-to-use or alternative recommendations beyond siblings listed.

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

Deploy Server