Skip to main content
Glama

case_export

Exports a full OSINT case as portable JSON, returning it inline or writing a secured file with path and digest so investigators can share, back up, or review evidence.

Instructions

Export a full case as portable JSON (entities, sources, observations, facts, image metadata).

Without out_path the JSON is returned inline; with out_path it is written to a file (JSON, 0o600 on POSIX) and only the path and digest are returned. Binary image files are not embedded; image rows carry their stored paths and hashes.

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": "<case>"
    },
    "name": "case_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
out_pathNo
max_itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the two output modes, POSIX file mode 0o600, and that binary images are excluded with paths/hashes recorded in rows. It omits whether it is read-only (implied but unstated via the file write) and, critically, what happens when the case exceeds max_items.

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?

Three tight sentences, front-loaded with the core action and payload, then the mode split, then the image caveat. No filler and no repetition of the schema.

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?

With no annotations and no output schema, the description does cover the return shape and file-mode side effects well. But max_items' truncation semantics and the meaning of the `case` argument (name vs identifier) are left entirely unaddressed, which leaves an agent unable to reason about export completeness.

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

Parameters5/5

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

Schema coverage is 0% and all three parameters lack descriptions, so the description must compensate — and it only partially does. It explains out_path's dual behavior in useful detail but never mentions max_items (default 5000), which can silently truncate a 'full case' export; that is a real semantic gap for a parameter that changes results.

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?

States a specific verb and resource ('Export a full case as portable JSON') and enumerates the payload contents (entities, sources, observations, facts, image metadata). It is clearly the exporter among case_* siblings, though it never names a sibling (e.g. case_list) for contrast.

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?

The description does give a usable decision rule for one parameter: omit out_path for inline JSON, supply it to write a file and get back only path + digest. It offers no guidance on when to export rather than use case_list/case_search, and no prerequisites or size expectations.

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