Skip to main content
Glama

darkseal_check

Check a sealed traversal capture by ID to obtain its verdict class and charged element names in a free counterparty view.

Instructions

Counterparty view: the verdict class and the names of charged elements only. 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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
capture_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description does carry some burden and does add real context: the output is deliberately limited to a verdict class plus charged element names, and the call is free (cost transparency). However, it says nothing about whether the check mutates or records state, whether it is idempotent, or what happens on an invalid capture_id.

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 compact sentences, front-loaded with the most decision-relevant fact (what the caller gets back) followed by the cost note. Nothing is wasted, though the brevity edges into under-specification rather than pure efficiency.

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

Completeness1/5

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

For a tool with no annotations, no output schema, and a required but undocumented identifier, the description leaves too much open. It omits what a capture_id is, what verdict classes mean, and whether the check has side effects, so an agent cannot confidently construct a call from this definition alone.

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 the single required parameter capture_id has no explanation in either the schema or the description. The agent is not told what a capture is, where a capture_id comes from, or what format it takes, so the description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description characterizes the response ("verdict class and the names of charged elements only") and implies a verification action via "the check is free," but never states plainly what the tool does to the input or what a "check" verifies. It hints at a distinction from siblings by calling itself the "counterparty view," yet names no alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative (e.g., darkseal_get_verdict) to route the agent toward a fuller view. The word "only" implies a more complete view exists elsewhere, but the agent must infer that.

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