aperture-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Liveness check; returns status + name + version. |
| compareA | 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. |
| compare_proposalA | compare specialized for a PROPOSAL: also flags strength regression (strong→weak wording) as degraded — but ONLY for a narrow FIXED keyword set (English modals + 必须/务必/应当/确保→应该/也许); most reworded/softened wording falls outside this list and is MISSED. Checks ONLY constraint/goal anchors (other kinds silently ignored) for presence in state_b. |
| compare_stanceB | compare specialized for a STANCE: also flags polarity reversal (support↔oppose) as degraded. Checks ONLY goal/baseline anchors (other kinds silently ignored) in state_b. |
| compare_commitmentA | compare specialized for a COMMITMENT: checks ONLY commitment anchors; flags a promise present in state_a but gone from state_b as DROPPED_SILENTLY. Caveat: cannot distinguish a FULFILLED commitment from an abandoned one — that disposition is the caller's to decide. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools are specialized but overlap with the generic `compare` tool, which can also handle stance, commitment, and proposal anchors. The specialized tools add narrow features but cause ambiguity in tool selection.
Four tools follow `compare_*` pattern, but `health` breaks the convention. The naming is mostly consistent with one clear outlier.
Five tools is slightly below what the domain might warrant (e.g., missing a baseline-specific comparison), but still reasonable and not too few.
Covers common comparison types but has gaps: missing a dedicated baseline comparison, and each specialized tool ignores certain anchor types. The generic `compare` has strict verbatim matching that may miss semantic equivalences.