Skip to main content
Glama

romm_get_item

Retrieve detailed metadata, user status, and save data for a specific ROM using its unique identifier.

Instructions

Get full detail for a single ROM — metadata, user status, saves.

rom_id: The ROM's ID (from romm_library_items or romm_search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rom_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'romm_get_item' function handles fetching and formatting ROM details from the Romm API. It is decorated with @mcp.tool(), which handles its registration.
    @mcp.tool()
    async def romm_get_item(rom_id: int) -> str:
        """Get full detail for a single ROM — metadata, user status, saves.
    
        rom_id: The ROM's ID (from romm_library_items or romm_search).
        """
        data = await _get(f"roms/{rom_id}")
    
        if not isinstance(data, dict) or "id" not in data:
            return f"ROM {rom_id} not found."
    
        name = data.get("name", "Unknown")
        slug = data.get("slug", "")
        platform = data.get("platform_display_name") or data.get("platform_slug", "?")
        summary = data.get("summary", "")
        size = data.get("fs_size_bytes", 0)
        regions = data.get("regions", [])
        languages = data.get("languages", [])
        tags = data.get("tags", [])
        alt_names = data.get("alternative_names", [])
    
        user = data.get("rom_user", {}) or {}
        is_fav = user.get("is_favorite", False) if isinstance(user, dict) else False
        last_played = user.get("last_played") if isinstance(user, dict) else None
        status = user.get("status") if isinstance(user, dict) else None
        note_raw = user.get("note_raw_markdown") if isinstance(user, dict) else None
    
        saves = data.get("user_saves", [])
        states = data.get("user_states", [])
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 the tool retrieves 'full detail' including metadata, user status, and saves, which hints at a read-only operation, but does not explicitly confirm it as non-destructive or safe. It also omits details like authentication requirements, rate limits, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded: the first sentence clearly states the tool's purpose, and the second sentence explains the parameter. There is no wasted text, and both sentences earn their place by adding value. However, it could be slightly more structured (e.g., separating usage notes), but overall it is efficient.

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 complexity (a single-parameter read operation), the description covers the basics: purpose and parameter semantics. An output schema exists, so the description need not explain return values. However, with no annotations and incomplete behavioral transparency (e.g., missing safety or auth details), the description is adequate but has clear gaps, making it minimally viable for 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 description adds meaningful context for the single parameter: it defines 'rom_id' as 'The ROM's ID (from romm_library_items or romm_search)', clarifying its source and purpose. With schema description coverage at 0% (the schema only specifies type and requirement), this compensates well by providing semantic value beyond the basic schema. Since there is only one parameter, the description adequately explains its role.

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: 'Get full detail for a single ROM — metadata, user status, saves.' It specifies the verb ('Get'), resource ('single ROM'), and scope of information returned. However, it does not explicitly differentiate from sibling tools like 'romm_library_items' or 'romm_search', which might also retrieve ROM details but in different contexts (e.g., lists vs. single items).

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: it mentions that rom_id can come from 'romm_library_items or romm_search', implying a prerequisite or data source. However, it does not specify when to use this tool versus alternatives (e.g., 'romm_search' for multiple ROMs or 'romm_library_items' for a list), nor does it outline any exclusions or specific contexts for usage. This lack of explicit when/when-not guidance limits its effectiveness.

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