VERDICT

Overview Schema Source Related Servers Discussions Admin

case_open

Open an investigation by listing evidence objects in the read-only evidence root and recording chain-of-custody hashes. Call this first to initialize a case.

Instructions

Open an investigation. Lists evidence objects in the read-only evidence root and records the chain-of-custody hash of each. Call this first.

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": {
      "case_name": "<case_name>"
    },
    "name": "case_open"
  }
}

Input Schema

Name	Required	Description	Default
`case_name`	Yes
`summary`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Without annotations, the description carries the transparency burden. It discloses that the tool lists evidence objects and records hashes, implying it is read-only. However, it does not state whether the tool creates a new case or requires an existing one, nor does it describe permissions or side effects.

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

Conciseness5/5

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

The description consists of two concise sentences with no extraneous information. It front-loads the primary action and adds behavioral details efficiently.

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?

Despite having an output schema, the description lacks context about prerequisites (e.g., case existence), return values, and parameter usage. For an entry-point tool, this incompleteness hinders agent understanding.

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

Parameters1/5

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

The input schema has 0% description coverage, and the description does not explain the 'case_name' or 'summary' parameters. The agent must infer their meaning from the tool name alone, which is insufficient.

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

Purpose5/5

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

The description clearly states the tool 'opens an investigation' and specifies the actions: listing evidence objects and recording chain-of-custody hashes. This distinguishes it from sibling tools that perform specific analyses.

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

Usage Guidelines4/5

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

The explicit instruction 'Call this first' provides clear guidance on when to use the tool. However, it does not mention when not to use it or any prerequisites.

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