Skip to main content
Glama

romm_devices

List registered devices like handhelds and emulators to manage and track your gaming hardware collection.

Instructions

List registered devices (handhelds, emulators, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for the 'romm_devices' MCP tool, which fetches and lists registered devices from the Romm API.
    @mcp.tool()
    async def romm_devices() -> str:
        """List registered devices (handhelds, emulators, etc.)."""
        data = await _get("devices")
    
        if not isinstance(data, list) or not data:
            return "No devices registered."
    
        lines = [f"Devices ({len(data)}):\n"]
        for d in data:
            name = d.get("name", "Unknown")
            device_type = d.get("type", "")
            device_id = d.get("id", "?")
    
            line = f"  - {name}"
            if device_type:
                line += f" ({device_type})"
            lines.append(line)
            lines.append(f"    ID: {device_id}")
    
        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. It states it lists devices but lacks behavioral details like whether it requires authentication, returns paginated results, includes metadata, or has rate limits. The description is minimal and does not disclose operational traits beyond the basic action.

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 zero waste. It is front-loaded with the core action and resource, making it easy to scan and understand quickly without redundancy or fluff.

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. However, as a listing tool with no annotations, it lacks context on behavior, output format, or usage scenarios, leaving gaps in completeness despite the structured data.

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 tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description appropriately does not discuss parameters, and the baseline score is 4 as it avoids unnecessary details while matching the schema's completeness.

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 the resource ('registered devices'), specifying the types (handhelds, emulators, etc.). It distinguishes from siblings by focusing on devices rather than collections, ROMs, or other entities, but does not explicitly contrast with similar tools like 'romm_library_items' or 'romm_platforms'.

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. It does not mention prerequisites, context, or exclusions, such as whether it lists all devices or only active ones, or how it differs from other listing tools like 'romm_platforms' or 'romm_library_items'.

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