Skip to main content
Glama

darkseal_diff_outcome

Diffs confirmation and charge artifact digests against sealed defaults, then mints a verdict flagging any charge or binding term that was pre-selected as PRESELECTED-AND-CHARGED.

Instructions

Diff the principal's own confirmation and charge artifacts (held as digests) against the sealed defaults and mint the verdict: a charge or binding term that began as a sealed pre-selected element verdicts PRESELECTED-AND-CHARGED naming that element. The check is free.

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": {
      "capture_id": "<capture_id>",
      "outcome_artifacts": "<outcome_artifacts>"
    },
    "name": "darkseal_diff_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
capture_idYes
outcome_artifactsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral load. It discloses two meaningful traits: the check has no cost ('free'), and a match mints the literal verdict label PRESELECTED-AND-CHARGED naming the offending element. It is silent on the negative case (what verdict/result when no preselected element was charged), whether the verdict is persisted, and failure behavior with missing or mismatched digests.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operation and its output are front-loaded in two sentences with no filler, but the second clause ('a charge or binding term that began as a sealed pre-selected element verdicts PRESELECTED-AND-CHARGED naming that element') is grammatically tangled and costs the reader a re-read.

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

Completeness2/5

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

For a tool with zero annotation coverage, 0% schema description coverage, a nested artifact object with an enum, and no output schema, the description leaves too much open: it describes only the positive verdict, not the alternative outcomes, the response shape, or whether a verdict is stored for later retrieval by darkseal_get_verdict.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate and it partly does: it makes clear artifacts are held as digests (artifact_digest), that a single element is identified (element_identity), and that the artifact kind is either a charge or a binding term, matching the enum. capture_id is left entirely unexplained and no format for the digests is given.

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 verb 'Diff...against the sealed defaults and mint the verdict' plus the named inputs (confirmation and charge artifacts held as digests) make the operation specific, and 'mint the verdict' usefully contrasts with the sibling darkseal_get_verdict, which presumably only retrieves. It falls short of 5 only because the phrasing is dense jargon and sibling differentiation is implicit rather than stated.

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?

'The check is free' implies it is safe to run unconditionally, which is light usage guidance. However, the description never states prerequisites (must capture_id exist, must darkseal_seal_defaults run first) or when to prefer darkseal_check or darkseal_recompute instead.

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