Skip to main content
Glama

darkseal_export_captures

Export a sealed capture with its receipt chain head and grammar version so you can independently recompute and verify agent-flow verdicts.

Instructions

Export a sealed capture (element states + seal) with the receipt chain head and grammar version, for independent recomputation. 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>"
    },
    "name": "darkseal_export_captures"
  }
}

Input Schema

NameRequiredDescriptionDefault
capture_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the contents of the export (element states, seal, receipt chain head, grammar version), which is genuine behavioral context, but it omits whether the operation is read-only and side-effect free, whether captures are retained or expire, permission requirements, and what "the check is free" actually means (cost, credits, or rate limits).

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?

Two short sentences with no filler, and the payload detail is front-loaded. However, the trailing clause "The check is free" is cryptic, sits outside the main purpose statement, and introduces ambiguity rather than information, so the second sentence does not fully earn its place.

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 single-parameter tool with no output schema and no annotations, the description covers content adequately but leaves gaps: it does not say whether the export is a JSON payload or a downloadable artifact, whether the operation is read-only, or how capture ids are obtained. That is enough to attempt a call, but not enough to call it confidently in edge cases.

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?

There is one required parameter, capture_id, at 0% schema description coverage, so the description must compensate and it only indirectly does so by using the word "capture." It adds no information about the identifier's format, where an agent obtains it, or what happens if the capture id is unknown; the "free" remark further complicates interpretation without clarifying the parameter.

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 gives a specific verb and resource ("Export a sealed capture") and enumerates the payload (element states, seal, receipt chain head, grammar version), so an agent knows what this produces. It is distinguishable from siblings like darkseal_recompute or darkseal_check because it explicitly frames the result as raw material for independent recomputation rather than performing the check itself.

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 phrase "for independent recomputation" implies the situation where an agent wants a portable artifact to verify elsewhere, and "The check is free" hints that verification costs nothing. However, there is no explicit when-not guidance, no mention of how this differs from darkseal_recompute or darkseal_get_verdict, and the "free" remark is left unexplained.

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