Skip to main content
Glama

case_image_similar

Find visually similar images already saved in a case by comparing dHash distance from a specified image, helping identify related or duplicate evidence.

Instructions

Find visually similar images already saved in this case using dHash distance.

Similarity is about the whole image and does not establish that two people are the same person. Exact copies also have the same SHA-256 digest.

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_id": "<image_id>"
    },
    "name": "case_image_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
image_idYes
max_distanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the comparison algorithm (dHash distance) and the semantic limit of the result. It also notes that exact copies share a SHA-256 digest, hinting at a duplicate-detection signal. It omits read-only/mutation status, whether results are ranked, and how many matches come back.

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 core action and mechanism. The SHA-256 sentence is slightly tangential but earns its place as a duplicate-detection caveat. No padding.

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 search tool with no output schema, no annotations, and 0% parameter coverage, the definition should describe the shape of results and the meaning of max_distance. Neither is covered, leaving meaningful gaps an agent must guess at.

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 case, image_id, and max_distance. Only 'dHash distance' implicitly gestures at max_distance as a threshold; nothing explains that lower means stricter, what units apply, or what case/image_id must reference.

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 and resource ('Find visually similar images') and scopes it precisely to images 'already saved in this case', plus names the mechanism (dHash distance). It doesn't explicitly contrast with siblings like case_image_view or image_analyze, 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 line 'Similarity is about the whole image and does not establish that two people are the same person' is a useful guardrail on how to interpret results, and 'already saved in this case' implies the input must be an indexed case image. However, it never says when to prefer this over case_image_view or image_analyze, nor any precondition such as the image needing to be added first.

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