Skip to main content
Glama

Reelagio Slot Database

List filter values

list_vocabulary
Read-only

List the exact providers, themes, features, mechanics, volatility levels and emoji tags used in the database, with how many slots have each. search_slots accepts close guesses, so call this only to show someone the options or when a search reports a value it did not recognise.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_vocabulary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds genuine behavioral context: it discloses that results are the exact in-database values accompanied by per-value slot counts, and that search_slots is fuzzy, which explains why this call is usually unnecessary. It stops short of describing ordering or result format details, so a 4 rather than a 5.

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?

Two sentences with no filler. The capability and its output shape come first, followed immediately by the usage constraint and the reason for it, so the reader hits the decision-relevant information early.

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?

With zero parameters and no output schema, the description must carry both routing and return-value expectations, and it does: it names the value categories returned, states that counts accompany each, and explains when the tool is unnecessary. Nothing an agent needs in order to select or call it is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. No misleading parameter language is present.

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 a precisely enumerated resource set (providers, themes, features, mechanics, volatility levels, emoji tags) plus the payload characteristic that each carries a slot count. Distinct from search_slots and get_slot, which retrieve slots rather than the vocabulary of filter values.

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 restriction ("call this only to show someone the options or when a search reports a value it did not recognise") and explains why by naming the alternative: search_slots accepts close guesses, so this tool is not needed for normal lookup. When-to-use and when-not-to-use are both covered.

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.

Resources