Skip to main content
Glama
Sign In

Systra Tools

by tools.systra
OverviewDiscussionsAdmin

List images

list_images
Read-onlyIdempotent

Lists images and a few videos from the Systra Tools media library (all AI-generated), each with a permanent URL to use directly as src, plus title, album and format. Filter by album and format, 100 per page. Use it to browse an album; use search_images to find a motif by keyword. Without a premium key only the free images are returned, three per album.

Input Schema

NameRequiredDescriptionDefault
pageNoPage of the result, 100 images per page (optional, default 1).
albumNoAlbum key (optional, German): verlaeufe, abstrakt, surreal, objekte, freisteller, natur, interior, essen, portraet, beauty, hochzeit, menschen, arbeitsplatz, business, industrie, gesundheit, sport, autos, luftfahrt, nachtleben. Without one, every album is returned.
formatNoImage format to filter by (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / album / description
      Previous value: -"Album key to filter by (optional), e.g. 'natur', 'business', 'abstrakt'. Without one, every album is returned."New value: +"Album key (optional, German): verlaeufe, abstrakt, surreal, objekte, freisteller, natur, interior, essen, portraet, beauty, hochzeit, menschen, arbeitsplatz, business, industrie, gesundheit, sport, autos, luftfahrt, nachtleben. Without one, every album is returned."
  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. Changed2 schema fields changed
    • changedInput schema / properties / album / description
      Previous value: -"Album-Schlüssel zum Filtern (optional), z. B. 'natur', 'business', 'abstrakt'. Ohne Angabe kommen alle Alben."New value: +"Album key to filter by (optional), e.g. 'natur', 'business', 'abstrakt'. Without one, every album is returned."
    • changedInput schema / properties / format / description
      Previous value: -"Bildformat zum Filtern (optional)."New value: +"Image format to filter by (optional)."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, but the description adds genuinely useful context: the returned fields and permanent URL usability as src, page size of 100, and the premium-key gating that silently narrows results. It stops short of saying how to detect the last page or why 'a few videos' appear in an image listing.

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?

Roughly four sentences, each doing distinct work: what it returns, how to filter, when to use vs the sibling, and the key limitation. Front-loaded with the resource and the result shape.

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

Completeness5/5

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

No output schema exists, so the description carries the return-shape burden and does so (URL, title, album, format). Combined with pagination size and quota gating, an agent has enough to call it correctly and interpret results.

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 coverage is 100% and the album enum values are fully enumerated there, so the description only restates filterable dimensions (album, format) and the 100-per-page cap. Baseline 3 is appropriate; no added syntax or semantics beyond the schema.

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+resource (lists images and a few videos) scoped to the Systra Tools media library, and names what each result carries (permanent URL, title, album, format). Clear enough to separate from search_images without opening the 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 routing rule: browse an album with this tool, use search_images to find a motif by keyword. It also states the access limitation (premium key yields only free images, three per album), which is the main precondition an agent needs.

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