Skip to main content
Glama

case_capture

Save source URLs and entity mentions from browser crawl or OSINT JSON results into a case record, storing short key sentences without raw page text or screenshots.

Instructions

Save source URLs and entity mentions from a browser_crawl/deep_osint JSON result.

Accepts an object with pages or a page list. Stores short key sentences, but not raw page text, screenshots, or inferred causal relationships.

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>",
      "result_json": "<result_json>"
    },
    "name": "case_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
result_jsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does disclose what is deliberately not persisted (raw page text, screenshots, inferred causal relationships), which is genuinely useful, but it says nothing about whether the case must already exist, deduplication behavior, permissions, or what happens on malformed input.

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 short sentences with no padding, and the core action is front-loaded. The second sentence is somewhat fragmentary ('Accepts an object with `pages` or a page list') but still conveys the accepted shape efficiently.

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-required-parameter mutation with no annotations and no output schema, the definition covers input shape and storage scope but leaves gaps: the meaning of `case`, expected return values, and preconditions. It is adequate but not complete for an agent invoking it cold.

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

Parameters3/5

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

Schema coverage is 0%, so both required parameters are undocumented in structured form. The description clarifies that result_json is a crawl result object containing `pages` or a page list, which adds real meaning for that parameter, but the `case` parameter is never explained (case id? name? must exist?).

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 (save) and specific resources (source URLs, entity mentions) and names the originating tools (browser_crawl/deep_osint), so the agent can tell what it produces. It does not explicitly distinguish itself from case_add_fact or other case_* writers, keeping it short of a 5.

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?

Usage is implied rather than stated: the tool is positioned as the capture step after a browser_crawl/deep_osint JSON result. There is no explicit when-not guidance or comparison to sibling case tools like case_add_fact, so the agent must infer the boundary.

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