Skip to main content
Glama

romm_collection_detail

Retrieve and display all ROMs within a specified collection to manage and organize your game library effectively.

Instructions

List ROMs in a specific collection.

collection_id: The collection's ID (from romm_collections).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that retrieves and formats the collection details using the ROMM API.
    async def romm_collection_detail(collection_id: int) -> str:
        """List ROMs in a specific collection.
    
        collection_id: The collection's ID (from romm_collections).
        """
        data = await _get(f"collections/{collection_id}")
    
        if not isinstance(data, dict) or "id" not in data:
            return f"Collection {collection_id} not found."
    
        name = data.get("name", "Unknown")
        desc = data.get("description", "")
        roms = data.get("roms", [])
    
        lines = [f"{name}"]
        if desc:
            lines.append(f"  {desc[:200]}")
        lines.append(f"  ROMs: {len(roms)}\n")
    
        if isinstance(roms, list):
            for i, rom in enumerate(roms[:50], 1):
                if isinstance(rom, dict):
                    rom_name = rom.get("name") or rom.get("rom_name", "Unknown")
                    platform = rom.get("platform_display_name") or rom.get("platform_slug", "")
                    line = f"  {i}. {rom_name}"
                    if platform:
  • server.py:708-709 (registration)
    Registration of the romm_collection_detail tool using the @mcp.tool() decorator.
    @mcp.tool()
    async def romm_collection_detail(collection_id: int) -> str:
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a listing operation, implying it's likely read-only and non-destructive, but doesn't confirm this or add any context about permissions, rate limits, pagination, or what the output contains. The description is too sparse to fully inform the agent about behavioral traits.

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 extremely concise with two sentences that directly address the tool's purpose and parameter semantics. It's front-loaded with the main action and wastes no words, making it easy for an agent to parse quickly.

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

Completeness4/5

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

Given the tool's low complexity (one parameter), the presence of an output schema (which handles return values), and the description's clear purpose and parameter guidance, it is reasonably complete. However, the lack of annotations and minimal behavioral context slightly limits completeness for safe invocation.

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 description adds meaningful context for the single parameter 'collection_id' by specifying it comes 'from romm_collections', which clarifies its source and relationship to another tool. With 0% schema description coverage and only one parameter, this compensates well, though it doesn't detail format constraints beyond being an integer.

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 ROMs') and resource ('in a specific collection'), making the purpose immediately understandable. It distinguishes from generic listing tools by specifying the collection scope, though it doesn't explicitly differentiate from all sibling tools like 'romm_library_items' or 'romm_search' which might also list ROMs.

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 minimal guidance, only implying usage when you have a collection ID from 'romm_collections'. It doesn't explain when to use this versus alternatives like 'romm_search' or 'romm_library_items', nor does it mention prerequisites 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