Skip to main content
Glama

romm_filters

Retrieve filter values like genres, regions, languages, and tags to refine ROM searches and organize game collections effectively.

Instructions

Get available filter values for ROM browsing — genres, regions, languages, tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the `romm_filters` tool which fetches filter data (genres, regions, etc.) from the ROMM API and formats it into a string summary.
    async def romm_filters() -> str:
        """Get available filter values for ROM browsing — genres, regions, languages, tags."""
        data = await _get("roms/filters", long_timeout=True)
    
        if not isinstance(data, dict):
            return "No filter data available."
    
        lines = ["Available ROM Filters:\n"]
    
        for key in ("genres", "franchises", "collections", "companies", "regions",
                    "languages", "tags"):
            values = data.get(key, [])
            if values:
                display = ", ".join(str(v) for v in values[:30])
                if len(values) > 30:
                    display += f"... (+{len(values) - 30} more)"
                lines.append(f"  {key.title()} ({len(values)}): {display}")
    
        if len(lines) == 1:
            return "No filters available (library may be empty)."
    
        return "\n".join(lines)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but does not cover key traits such as whether it's read-only, requires authentication, has rate limits, or what the output format entails. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Get available filter values for ROM browsing') and lists the specific value types without any wasted words. It is appropriately sized for a tool with no parameters and clear functionality.

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?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. It explains what the tool returns (filter values) but lacks details on behavioral aspects like authentication or rate limits, which are important for a tool in a ROM management context. The output schema may cover return values, but the description could be more complete by addressing usage context.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by specifying the types of filter values (genres, regions, languages, tags), which provides semantic context beyond the empty schema, earning a score above the baseline of 3 for high schema coverage.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('available filter values for ROM browsing'), and it enumerates the types of values (genres, regions, languages, tags). However, it does not explicitly differentiate from sibling tools like 'romm_search' or 'romm_library_items', which might also involve filtering or browsing, leaving some ambiguity about its unique role.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context (e.g., before performing a search), or exclusions, leaving the agent to infer usage based on the purpose alone without explicit direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lodordev/mcp-romm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server