Skip to main content
Glama
Sign In

Systra Tools

by tools.systra
OverviewDiscussionsAdmin

Search images

search_images
Read-onlyIdempotent

Finds images in the media library (all AI-generated) whose title, tags, file name or album contain every word of the query, and returns their permanent URLs, 100 per page. Use it for a motif, such as 'red dress', 'laptop desk' or 'misty forest'; use list_images to browse a whole album. Titles and tags are English, album keys German. Without a premium key only the free images are included.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage of the result, 100 images per page (optional, default 1).
queryYesOne or more words; every word must match. E.g. 'gradient', 'laptop', 'red dress'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search term, e.g. 'gradient', 'laptop', 'wald'."New value: +"One or more words; every word must match. E.g. 'gradient', 'laptop', 'red dress'."
  2. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page of the result, 100 images per page (optional, default 1).",
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Suchbegriff, z. B. 'gradient', 'laptop', 'wald'."New value: +"Search term, e.g. 'gradient', 'laptop', 'wald'."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words elsewhere: results are all AI-generated, 100 per page, returned as permanent URLs, and licensing limits the corpus for non-premium keys. The language note (titles/tags English, album keys German) is non-obvious operational context an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences: what it matches and returns first, then the routing versus list_images, then the licensing caveat. No restatement of the name or title, and no filler.

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?

For a two-parameter search with no output schema, the description covers matching semantics, return payload (permanent URLs), page size, and corpus restrictions. It stops short of saying whether results are relevance-ordered or how to detect the last page, a minor gap for a paginated tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline would be 3. The description adds value beyond that by clarifying the AND-match semantics across multiple fields and by noting that album keys are German while titles/tags are English, which materially affects how to phrase a query.

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?

States a specific verb and resource ('Finds images in the media library') plus the exact matching rule: every word of the query must appear in title, tags, file name or album. It also names the sibling it is not ('use list_images to browse a whole album'), so an agent can separate it from the browse tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use with concrete examples ('red dress', 'laptop desk', 'misty forest') and an explicit alternative with its own condition (list_images for browsing a whole album). It also discloses a prerequisite that changes results: without a premium key only free images are returned.

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

All Systra Tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources