Skip to main content
Glama

case_add_fact

Add a sourced relationship to an OSINT case with evidence, storing it as an unverified lead if no source is supplied.

Instructions

Add an explicit relationship to a case, with a source and short evidence quote.

Without a source, it is stored as an unverified lead. Never infer causality or identity merely because two entities appear on the same page.

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>",
      "subject": "<subject>",
      "predicate": "<predicate>",
      "object_name": "<object_name>"
    },
    "name": "case_add_fact"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
subjectYes
evidenceNo
predicateYes
source_urlNo
object_kindNoperson
object_nameYes
subject_kindNoperson

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one meaningful behavior: facts submitted without a source are persisted as an unverified lead. It does not cover permissions, deduplication of existing facts, or whether entries can be edited or removed later.

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?

Three short sentences with the core action front-loaded and the grounding rule immediately after. Little waste, though the second and third sentences could be merged without loss.

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 an 8-parameter mutation tool with no annotations and no output schema, the description conveys the epistemic model (sourced vs unverified) but omits the kind fields and any indication of what is returned after a fact is added. Adequate but clearly incomplete.

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 description coverage is 0% across 8 parameters, so the description must compensate. It implicitly maps to source_url and evidence ('with a source and short evidence quote'), but leaves subject_kind and object_kind (defaulting to 'person'), predicate shape, and the case identifier unexplained.

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 states a specific verb and resource: 'Add an explicit relationship to a case', and clarifies the payload consists of a source plus evidence quote. This distinguishes it from note- or capture-style case tools, though it never names a sibling explicitly.

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 by the constraint 'Never infer causality or identity merely because two entities appear on the same page', which tells the agent what kinds of facts to submit. It stops short of saying when to prefer this over a case note or capture tool, or what prerequisites exist.

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