Skip to main content
Glama

case_create

Create or reopen a local investigation case, storing all data in a private SQLite file so OSINT work stays organized and revisitable.

Instructions

Create or reopen a local investigation case. Data stays in a private SQLite file.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/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. 'Data stays in a private SQLite file' is genuinely useful context about storage and privacy, and 'reopen' hints that an existing name does not error out. But it says nothing about permissions, whether an existing case is modified or returned untouched, or what the call yields, so an agent cannot predict the outcome of a name collision.

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?

Two short sentences, front-loaded with the operation and followed by the one piece of environmental context that matters. No filler or redundancy.

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 two-parameter, non-destructive creation tool with no output schema, the essentials are mostly covered. However, an agent still cannot tell whether reopening preserves or replaces an existing case's contents, nor what identifier comes back to use with the other case_* tools.

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 two parameters, so the schema alone gives no meaning. The description only indirectly implies that 'name' is the identity key used for lookups and reopening; it never explains the format of 'name' or what 'description' is used for, leaving the burden unmet.

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 phrase ('Create or reopen') and resource ('local investigation case'), which clearly separates it from sibling tools like case_add_fact or case_list that operate on an existing case. It stops short of naming any sibling explicitly, but the operation is unambiguous.

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?

'Create or reopen' implies the call is safe to repeat and is the natural first step before the case_* tools, but the description never says when to use this versus case_list or case_search, nor what happens if the case already exists beyond the word 'reopen'. Usage is implied rather than stated.

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