Skip to main content
Glama

Axad

Find pictures

find_images
Read-only

Search the shared image library for pictures that show a word, chunk, action or scene. query is a literal English description of the picture and lang the language of the concept. Returns up to 8 pictures, best fit first, each with a library id, title and concept.

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

Input Schema

NameRequiredDescriptionDefault
langYesBCP 47 code of the concept: pictures with words in another language are left out.
queryYesA literal English description of the picture you want: "a patient in a doctor's waiting room, reading a magazine".
conceptNoThe language element it should teach, in its language: "la sala de espera".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is provided structurally. The description adds real value by describing the result shape: at most 8 hits, best fit first, each carrying a library id, title, and concept. It says nothing about empty-result behavior or whether results are stable across repeats (idempotentHint=false).

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 with the core purpose front-loaded and no filler. The final sentence on result count and fields is doing useful work rather than padding.

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

Completeness4/5

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

With no output schema, the description correctly shouldered the burden of explaining what comes back (up to 8 items, ordered, with id/title/concept). The only gaps are edge behavior on zero matches and the role of the optional concept filter.

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 100%, so the schema already defines all three parameters, including the BCP 47 constraint on lang. The description restates the query and lang meanings with only a small added nuance ('literal English description') and leaves the optional concept parameter unaddressed, so it stays at the baseline.

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?

It gives a specific verb and resource ('search the shared image library for pictures') and constrains the content type to words, chunks, actions, or scenes. It is clearly a library lookup that returns ids rather than a display tool, though it never names a sibling (e.g. show_picture, nominate_image) to sharpen the boundary.

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?

Usage is only implied by the content list: you use it when you need to locate a picture for a concept. There is no explicit statement of when to prefer this over showing or nominating an image, and no exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.