Skip to main content
Glama

case_note

Save an entity with a short observation note and optional source URL to record evidence or leads in an OSINT case.

Instructions

Save a person, place, event, organization, or other entity with a short note.

A source URL records where the observation came from. Notes are evidence excerpts or leads, not proof of a relationship to another entity.

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>",
      "entity": "<entity>",
      "kind": "<kind>",
      "observation": "<observation>"
    },
    "name": "case_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
kindYes
entityYes
source_urlNo
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It clarifies that source_url records provenance and that notes are evidence rather than proof, but it does not disclose mutation behavior, permissions, duplicate handling, reversibility, or return behavior.

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?

The description is short and front-loads the main action before adding the evidentiary caveat. It is efficient, though the second paragraph is somewhat abstract and could more directly support invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with five parameters, four required, no annotations, no output schema, and 0% schema description coverage, the description is too thin. It does not explain required fields like 'case' and 'kind,' nor does it address duplicate handling or expected outcomes.

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%, so the description must compensate for all five parameters. It adds meaning for entity types, observation as a 'short note,' and source_url as provenance, but leaves the required 'case' and 'kind' parameters entirely 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 uses a specific verb ('Save') and resource ('person, place, event, organization, or other entity with a short note'), making the core action clear. However, it does not distinguish this tool from siblings such as case_add_fact or case_capture, so it falls 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?

The description gives a useful semantic boundary: notes are 'evidence excerpts or leads, not proof of a relationship to another entity,' which implies when not to use it for relationship claims. It does not explicitly name alternatives or say when to prefer case_add_fact, case_capture, or other sibling tools.

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