Skip to main content
Glama

case_research

Run deep OSINT research for a case, automatically saving discovered sources and entity mentions and returning original results with capture counts.

Instructions

Run deep_osint, then automatically save discovered sources and entity mentions.

Returns the original research result plus capture counts. Facts about who did what or why require case_add_fact with source evidence.

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>",
      "query": "<query>"
    },
    "name": "case_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
queryYes
max_pagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description still discloses the key mutation behavior: it automatically saves discovered sources and entity mentions, returns capture counts, and requires case_add_fact for who/what/why facts. It omits details such as permissions, rate limits, duplicate handling, and error behavior.

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 is three tight sentences, front-loaded with the action and return value. The fact-handling constraint earns its place by preventing misuse.

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 composite tool with no annotations and no output schema, the description covers the core behavior and return summary adequately. However, with 0% parameter description coverage, it leaves required case/query and max_pages unexplained, so it is not fully complete.

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?

Schema description coverage is 0%, and the description never mentions case, query, or max_pages. It adds no meaning for any of the three parameters, leaving the agent to rely on bare schema titles.

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 states a specific composite action: run deep_osint, automatically save discovered sources and entity mentions, and return the original result plus capture counts. It also names case_add_fact for facts, making it distinguishable from that sibling.

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?

It gives clear context for case-scoped research with automatic capture and explicitly routes facts to case_add_fact with source evidence. It does not explicitly say when to choose this over using deep_osint alone, so it stops short of perfect guidance.

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