Skip to main content
Glama

darkseal_recompute

Recompute a verdict from an exported capture, element grammar version, and outcome artifacts without requiring service state. Verify results offline and for free.

Instructions

Recompute a verdict from an exported capture plus the element grammar version plus the outcome artifacts, with no service state. 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": "<capture>",
      "grammar_version": "<grammar_version>",
      "outcome_artifacts": "<outcome_artifacts>"
    },
    "name": "darkseal_recompute"
  }
}

Input Schema

NameRequiredDescriptionDefault
captureYes
grammar_versionYes
outcome_artifactsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden; it does disclose two useful traits (no service state required, and that the check is free/no cost). It says nothing about what happens when grammar_version does not match the capture, whether anything is persisted, or how failures surface, which are the main behavioral risks for a recomputation tool.

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?

Two short sentences, front-loaded with the operation and its inputs; nothing is padded. The closing sentence about the check being free is unusual in placement but does carry cost information an agent may care about.

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 three-required-parameter tool with nested objects, no annotations, and no output schema, the description is thin: it never characterizes the returned verdict, mismatch handling, or artifact semantics. It does cover the essential framing (offline recompute from capture plus grammar version plus artifacts), so it is minimally viable but not complete.

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

Parameters2/5

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

Schema description coverage is 0% and all three parameters are required with a nested artifact object containing an enum (charge, binding-term), so the description must compensate. It only restates the parameter names in prose and adds no meaning about capture structure, accepted grammar_version format, or what the two artifact kinds represent.

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 pairs a specific verb ('Recompute') with a specific resource ('a verdict') and names all three inputs, so the agent knows exactly what the tool produces. It does not name or contrast any sibling such as darkseal_check or darkseal_get_verdict, so the distinction is left to inference from 'with no service state'.

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?

'with no service state' implies the usage condition (offline/pure recomputation rather than a live service lookup), which is the closest thing to when-to-use guidance present. There is no explicit exclusion or named alternative, so the agent must infer that darkseal_check is the stateful counterpart.

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