Skip to main content
Glama

darkseal_get_verdict

Fetch the complete verdict record for a capture to verify charged elements, grammar version, and receipt references.

Instructions

The full verdict record for a capture: verdict, charged element names, grammar version, coverage statement, separation marker, receipt refs. 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_get_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
capture_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, and it discloses only that the operation is free and what fields come back. It does not say whether this is a read-only lookup or whether it triggers/refreshes a check, whether the capture must already exist, or what happens on an unknown capture_id — a significant gap for a tool whose name suggests possible computation.

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 tight sentences with the returned payload front-loaded and the cost note trailing. Nothing is redundant, though the fragmentary noun-phrase style leaves the action implicit.

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?

The field list partially substitutes for the absent output schema, which is genuinely useful. But with no annotations, no output schema, and an undocumented parameter, the definition still leaves the read-vs-compute nature and error conditions unstated.

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% for the single parameter capture_id, so the description must compensate. 'For a capture' only loosely signals that the ID identifies a capture; it gives no format, no source (where to obtain an ID), and no behavior for invalid IDs.

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 names the resource precisely (the full verdict record for a capture) and enumerates its contents — verdict, charged element names, grammar version, coverage statement, separation marker, receipt refs. It never uses a verb (retrieve/fetch) and does not distinguish itself from the sibling darkseal_check, so an agent must infer whether this reads a stored verdict or runs a new check.

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 and no mention of when not to use it. The sibling darkseal_check is the obvious alternative and the definition gives no condition that selects between them; 'The check is free' is a cost remark, not a routing rule.

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