Skip to main content
Glama

find_images

Locate image files in a directory and narrow results by filename pattern, tag, minimum rating, or modification date. Use it to filter large photo libraries down to the specific images you need.

Instructions

Find images under a directory, optionally filtered by filename pattern (glob), tag, minimum rating (0-5) or modification date (ISO, e.g. 2025-01-01).

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": {
      "directory": "<directory>"
    },
    "name": "find_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNo
directoryYes
min_ratingNo
newer_thanNo
older_thanNo
name_patternNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.7/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 implies a read-only search but does not disclose whether traversal is recursive, how limit interacts with results, permission requirements, pagination behavior, or anything about the returned image set.

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 single sentence is front-loaded with the core action and scoping, and it includes useful examples for the date format. It is efficient, though a 7-parameter tool might benefit from slightly more structured presentation.

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?

Given 7 parameters, zero schema descriptions, and no annotations, the description is not complete enough for reliable invocation. An output schema exists, so return values need not be explained, but parameter behavior and filtering edge cases remain under-specified.

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% across 7 parameters, so the description must compensate. It explains directory, name_pattern as glob, tag, min_rating range 0-5, and ISO date format, but omits 'limit' entirely and does not clarify the distinction between 'newer_than' and 'older_than' or their default null behavior.

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 images') and names the scope ('under a directory') plus supported filters. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling 'find_images_by_tags' despite overlapping tag-filtering capability.

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

Usage Guidelines2/5

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

The description says the filters are optional but gives no guidance on when to use this tool versus alternatives such as find_images_by_tags. There are no exclusions, prerequisites, or decision criteria for an agent to choose between siblings.

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