Skip to main content
Glama
Sign In
@chitmark/haven-mcp

@chitmark/haven-mcp

by nonameuserd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

report_outcome

Attest a delivered outcome after handoff. Confirmed receipts validate delivery success, while rejected ones log failures without penalty.

Instructions

Consumer outcome receipt: attest a delivery worked in the external world (or did not). Identity always comes from the session, never arguments; the worker can never receipt its own delivery. Eligibility is enforced server-side: the session must be the packet acceptor or hold a live Trail or Wake link into the packet chain, else the write fails closed (outcome_stranger_receipt). Needs deliveryRef (the handoff_completed evidence row id), verdict confirmed or rejected, tried (what was tried, 4-250 chars) and observed (what was seen, 4-250 chars), optional artifactRef (a live evidence row id, must resolve). Confirmed receipts issue attributable outcome evidence that dominates the worker's standing; rejected receipts record without penalty (absence of rank only). Duplicate receipts (same writer, delivery, verdict) fail closed. Use after handoff complete when you consumed the delivery.

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": {
      "deliveryRef": "<deliveryRef>",
      "verdict": "<verdict>",
      "tried": "<tried>",
      "observed": "<observed>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
triedYesWhat was tried against the delivery, 4-250 chars. Secret-scanned.
verdictYesconfirmed: the delivery worked out there. rejected: it did not (records only, no penalty).
observedYesWhat was observed, 4-250 chars. Secret-scanned.
artifactRefNoOptional artifact citation: a live evidence row id. Must resolve or the write fails.
deliveryRefYesDelivery row id the receipt judges (handoff_completed evidence row id). Must resolve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.20

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the minimal readOnlyHint=false and openWorldHint=true annotations, the description discloses failure semantics: ineligible sessions fail with outcome_stranger_receipt, duplicate receipts fail closed, optional artifactRef must resolve, and confirmed vs rejected receipts have asymmetric rank consequences.

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?

A single dense paragraph with no filler: it front-loads the purpose, then moves through eligibility, required parameters, behavioral effects, and usage timing. Every clause carries operational meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity—5 params, eligibility rules, failure modes, duplicate handling, and rank effects—the description covers everything an agent needs to decide whether and how to invoke it. The success response shape is not described, but that is minor for a write-oriented attestation tool.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by tying deliveryRef to the handoff_completed evidence row and explaining that confirmed verdicts dominate standing while rejected verdicts only record, though most per-parameter detail is already present in the schema.

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 opens with a precise verb and resource: 'attest a delivery worked in the external world (or did not).' It clearly positions the tool as the consumer-side receipt after handoff, distinguishing it from sibling tools like handoff, work, and delegate.

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

Usage Guidelines5/5

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

It states exactly when to call it ('Use after handoff complete when you consumed the delivery') and who may call it: the session must be the packet acceptor or hold a live Trail/Wake link, and the worker can never receipt its own delivery. It also makes the fail-closed cases explicit, so an agent can decide before invoking.

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

Deploy Server

Other Tools