Skip to main content
Glama

romm_smart_collections

List auto-generated, rule-based collections to organize and manage your ROM library efficiently.

Instructions

List auto-generated smart collections (rule-based).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `romm_smart_collections` tool handler, which fetches smart collections from the ROMM API and formats them for the user.
    @mcp.tool()
    async def romm_smart_collections() -> str:
        """List auto-generated smart collections (rule-based)."""
        data = await _get("collections/smart")
    
        if not isinstance(data, list) or not data:
            return "No smart collections found."
    
        lines = [f"Smart Collections ({len(data)}):\n"]
        for c in data:
            name = c.get("name", "Unknown")
            desc = c.get("description", "")
            cid = c.get("id", "?")
    
            lines.append(f"  {name}")
            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)
    
    
    # ── Tools — Saves & User Status ──────────────────────────────────────────
Behavior2/5

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

With no annotations, the description carries full burden but only states it lists collections without disclosing behavioral traits like pagination, sorting, error conditions, or rate limits. It mentions 'auto-generated' and 'rule-based' which add some context, but overall transparency is minimal.

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 with no wasted words. It is front-loaded with the core action and resource, making it highly concise and well-structured.

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 0 parameters, 100% schema coverage, and an output schema, the description is adequate but minimal. It lacks context on when to use versus siblings and behavioral details, which could be important for a list operation in a server with many similar tools.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on tool purpose without redundant parameter info, meeting the baseline for zero-parameter tools.

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 ('auto-generated smart collections'), with the qualifier 'rule-based' adding specificity. It distinguishes from sibling 'romm_collections' by specifying 'smart' collections, though not explicitly contrasting them.

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?

No guidance is provided on when to use this tool versus alternatives like 'romm_collections' or 'romm_search'. The description implies it's for listing smart collections, but lacks explicit usage context or exclusions.

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