Skip to main content
Glama

MGS Toolbox

by com.michaelghelfistudios
OverviewDiscussionsAdmin

List / filter a catalogue

list_entries

A page of one catalogue, filtered. Use it to answer "which minerals are cubic and gem-quality?", "legendary metals of the medieval era", "swamp ingredients with a fire essence". Combine with q for a name search inside the filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
kindYesWhich catalogue: metal, mineral, ingredient, potion, gem, milieu, animal, plant, monster, hearth_page, passage_page, bearer_page.
langNoLanguage of the texts: en (default), fr, or all for both.
limitNo
offsetNo
filtersNoField filters as {name: "value" | "value1,value2"} (any-of, case-insensitive). Names per catalogue: metal → category, era, rarity, fictional, tag; mineral → type, system, rarity, gem_quality, color, magic, planar_origin, origin; ingredient → category, rarity, realm, biome, landform, structure, qualifier, essence, creature_type, part; potion → essence; gem → color, rarity, temporary; milieu → realm, group; animal → kind, size, danger, activity, domestic and the place filters; plant → kind and the place filters; monster → type, size, cr, danger and the place filters; hearth_page, passage_page, bearer_page → none (search by name with q). list_facets gives the values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / filters / description
      Previous value: -"Field filters as {name: \"value\" | \"value1,value2\"} (any-of, case-insensitive). Names per catalogue: metal → category, era, rarity, fictional, tag; mineral → type, system, rarity, gem_quality, color, magic, planar_origin, origin; ingredient → category, rarity, realm, biome, landform, structure, qualifier, essence, creature_type, part; potion → essence; gem → color, rarity, temporary. list_facets gives the values."New value: +"Field filters as {name: \"value\" | \"value1,value2\"} (any-of, case-insensitive). Names per catalogue: metal → category, era, rarity, fictional, tag; mineral → type, system, rarity, gem_quality, color, magic, planar_origin, origin; ingredient → category, rarity, realm, biome, landform, structure, qualifier, essence, creature_type, part; potion → essence; gem → color, rarity, temporary; milieu → realm, group; animal → kind, size, danger, activity, domestic and the place filters; plant → kind and the place filters; monster → type, size, cr, danger and the place filters; hearth_page, passage_page, bearer_page → none (search by name with q). list_facets gives the values."
    • changedInput schema / properties / kind / description
      Previous value: -"Which catalogue: metal, mineral, ingredient, potion or gem."New value: +"Which catalogue: metal, mineral, ingredient, potion, gem, milieu, animal, plant, monster, hearth_page, passage_page, bearer_page."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "metal",
-  "mineral",
-  "ingredient",
-  "potion",
-  "gem"
-]New value: +[
+  "metal",
+  "mineral",
+  "ingredient",
+  "potion",
+  "gem",
+  "milieu",
+  "animal",
+  "plant",
+  "monster",
+  "hearth_page",
+  "passage_page",
+  "bearer_page"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / filters / description
      Previous value: -"Field filters as {name: \"value\" | \"value1,value2\"} (any-of, case-insensitive). Names per catalogue: metal → category, era, rarity, fictional, tag; mineral → type, system, rarity, gem_quality, color, magic, planar_origin, origin; ingredient → category, rarity, environment, essence, tag; potion → essence; gem → color, rarity, temporary. list_facets gives the values."New value: +"Field filters as {name: \"value\" | \"value1,value2\"} (any-of, case-insensitive). Names per catalogue: metal → category, era, rarity, fictional, tag; mineral → type, system, rarity, gem_quality, color, magic, planar_origin, origin; ingredient → category, rarity, realm, biome, landform, structure, qualifier, essence, creature_type, part; potion → essence; gem → color, rarity, temporary. list_facets gives the values."
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description bears the full load. 'A page of' does hint at paginated reads and the examples show the filter-combination behavior, but it never states whether the operation is read-only, how results are ordered, or what the default page size is — gaps that carry real weight with zero annotation coverage.

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?

Front-loaded with the core statement, then usage examples. The three quoted questions are longer than strictly needed for a 10-word capability, but they carry real disambiguating value rather than being filler.

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

Completeness3/5

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

For a 6-parameter tool with a nested filters object, no annotations, and no output schema, the description covers query construction reasonably (via the schema's filter documentation) but leaves the response shape — page size, total counts, ordering — entirely undisclosed.

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 descriptions cover roughly half the parameters, with 'kind', 'lang', and 'filters' well documented inline (including the full per-catalogue field list). The description adds that q is a name search that composes with filters, but says nothing about limit/offset or the lang default beyond the schema's own note.

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 concrete verb+resource: returns a filtered page of a single catalogue. The three quoted example questions ('which minerals are cubic and gem-quality?') make the intended query shape concrete. It doesn't explicitly distinguish itself from get_entry, random_entry, or list_facets, so it stops short of a 5.

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?

The example questions imply when to reach for this tool (multi-criteria catalogue lookups) and 'Combine with q for a name search inside the filter' adds one concrete usage rule. However, nothing states when NOT to use it, nor routes the agent to get_entry for single items or list_facets for valid filter values.

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

All MGS Toolbox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources