Skip to main content
Glama

case_image_add

Save and analyze a local or remote image within a case, then optionally file it under a person for organization without uploading the image.

Instructions

Save a local/remote image in a case, analyze it, and optionally file it under a person.

Assigning a person labels the file for organization; it does not identify the face or prove who appears in the image. No image is uploaded by this tool.

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>",
      "image": "<image>"
    },
    "name": "case_image_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocrNo
caseYes
imageYes
personNo
source_urlNo

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 disclosure burden. It does add genuinely useful behavioral facts — no upload occurs (local processing), and person attribution is not a face-match claim — but it never says whether the image record becomes part of persistent case state, what 'analyze' performs, or what permissions/errors to expect.

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, front-loaded with the action and immediately followed by the one caveat most likely to be misread. The middle sentence earns its place as a disambiguation; nothing is padding, though the phrasing could be tighter.

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 5-parameter mutation-like tool with zero annotation coverage and no output schema, the description covers the headline action and the person caveat but leaves the OCR toggle, the remote-source parameter, and any notion of what is returned unaddressed. An agent could invoke it correctly in the common case but would be guessing on two parameters.

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 5 parameters, so the description must compensate and only partly does: it explains that image may be local or remote (hinting at source_url) and clarifies the semantics of person. The ocr boolean (default true) is never mentioned, and source_url is only indirectly implied, leaving two of five parameters' meaning to inference.

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 leads with a specific compound verb phrase: save a local/remote image in a case, analyze it, and optionally file it under a person. That is concrete enough to separate it from read-only siblings like case_image_view and from transforms like case_image_crop or case_image_similar, though it never names those alternatives 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?

It implies the usage context (creating a case image record, optionally attributing it to a person) and gives one useful exclusion — that assigning a person is organizational labeling, not face identification. It does not state when an agent should pick this over image_analyze or case_image_reverse, or what preconditions a case must satisfy.

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