Skip to main content
Glama
Sign In
EAD Factory MCP Server

EAD Factory MCP Server

Official
by g-digital-by-Garrigues
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

evidence_thumbnail_url_get

Read-onlyIdempotent

Get a temporary thumbnail URL for image evidence at any size, enabling quick visual verification without downloading the original file.

Instructions

Retrieves a temporary URL for an image evidence's thumbnail at the requested size — use for quick visual verification without downloading the original file. Requires: caseFileId + evidenceGroupId + evidenceId (image-type evidence only) and a thumbnailSize path value.

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": {
      "caseFileId": "<caseFileId>",
      "groupId": "<groupId>",
      "evidenceId": "<evidenceId>",
      "thumbnailSize": "<thumbnailSize>"
    },
    "name": "evidence_thumbnail_url_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYes
caseFileIdYesMANDATORY. UUID of the parent case file. Obtain from evidence_case_file_create.
evidenceIdYesMANDATORY. UUID of the evidence record. Obtain from evidence_group_evidence_register or generate_evidence.
thumbnailSizeYes

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
typeNo
expirationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate readOnly and nondestructive behavior; the description adds meaningful behavioral context: the URL is temporary, it is for thumbnails only, and it avoids downloading the original. This goes beyond the structured safety hints without contradicting them.

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 brief and front-loaded with the core purpose in the first sentence, followed by requirements. However, the naming error ('evidenceGroupId' vs 'groupId') slightly undermines its otherwise efficient structure.

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?

While a simple read tool with output schema and safety annotations, the description is not fully complete: the parameter naming inconsistency could cause invocation errors, and thumbnailSize semantics are unexplained. These are material gaps for correct usage.

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 coverage is only 50%, and the description must compensate but fails to do so adequately. It lists 'caseFileId + evidenceGroupId + evidenceId', but the actual schema parameter is 'groupId', creating a naming mismatch. It adds no meaningful detail for 'thumbnailSize' (e.g., accepted values), leaving two parameters under-described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a temporary thumbnail URL for image evidence, specifying the exact verb and resource. It distinguishes itself from sibling download URL tools by emphasizing 'thumbnail' and 'without downloading the original file', making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'use for quick visual verification without downloading the original file', providing clear context. It also notes 'image-type evidence only', which sets a boundary, though it does not name alternative tools for other use cases.

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

Deploy Server

Other Tools