Skip to main content
Glama

romm_collections

List user-curated collections to organize and manage your ROM library effectively.

Instructions

List user-curated collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `romm_collections` fetches collections data and formats it as a string for the MCP client.
    async def romm_collections() -> str:
        """List user-curated collections."""
        data = await _get("collections")
    
        if not isinstance(data, list) or not data:
            return "No collections found."
    
        lines = [f"Collections ({len(data)}):\n"]
        for c in data:
            name = c.get("name", "Unknown")
            desc = c.get("description", "")
            cid = c.get("id", "?")
            roms = c.get("roms", [])
            rom_count = len(roms) if isinstance(roms, list) else 0
    
            lines.append(f"  {name} ({rom_count} ROM{'s' if rom_count != 1 else ''})")
            if desc:
                short = desc[:100]
                if len(desc) > 100:
                    short += "..."
                lines.append(f"    {short}")
            lines.append(f"    ID: {cid}")
            lines.append("")
    
        return "\n".join(lines)
  • server.py:680-680 (registration)
    The `romm_collections` tool is registered using the `@mcp.tool()` decorator.
    @mcp.tool()
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 'List user-curated collections,' which implies a read-only operation, but does not specify details like authentication requirements, rate limits, pagination, or what 'user-curated' entails. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no wasted words, making it highly concise and front-loaded. It directly communicates the core purpose without unnecessary elaboration, which is ideal for a simple tool.

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's simplicity (0 parameters, output schema provided), the description is adequate but minimal. It covers the basic purpose but lacks context on behavior and usage relative to siblings. With no annotations and an output schema, it meets minimum viability but could be more informative about operational details.

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 the schema fully documents the absence of inputs. The description does not add parameter information, which is unnecessary here. A baseline of 4 is appropriate as the schema handles all parameter semantics effectively.

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 action ('List') and resource ('user-curated collections'), making the purpose understandable. However, it does not differentiate this tool from sibling tools like 'romm_smart_collections' or 'romm_collection_detail', which might handle similar or overlapping data, so it misses full sibling distinction.

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, such as 'romm_smart_collections' or 'romm_collection_detail'. It lacks context on prerequisites, exclusions, or specific use cases, leaving the agent to infer usage based on the name alone.

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