Skip to main content
Glama

romm_firmware

List BIOS and firmware files for ROM management, with optional filtering by platform to organize your collection.

Instructions

List BIOS/firmware files. Optionally filter by platform.

platform_id: Filter to a specific platform (0 = all).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platform_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `romm_firmware` tool is implemented as an async function decorated with `@mcp.tool()`. It takes an optional `platform_id` and fetches firmware data from the RomM API using a helper function `_get`.
    @mcp.tool()
    async def romm_firmware(platform_id: int = 0) -> str:
        """List BIOS/firmware files. Optionally filter by platform.
    
        platform_id: Filter to a specific platform (0 = all).
        """
        params: dict = {}
        if platform_id:
            params["platform_id"] = platform_id
    
        data = await _get("firmware", params=params)
    
        if not isinstance(data, list) or not data:
            qualifier = f" for platform {platform_id}" if platform_id else ""
            return f"No firmware found{qualifier}."
    
        lines = [f"Firmware ({len(data)}):\n"]
        for fw in data[:50]:
            fname = fw.get("file_name", "?")
            size = fw.get("file_size_bytes", 0)
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's a listing tool, implying read-only behavior, but doesn't disclose any behavioral traits such as pagination, rate limits, authentication needs, or what happens if no files match. For a tool with no annotation coverage, this leaves significant gaps in understanding its operation.

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 and front-loaded: the first sentence states the core purpose, and the second adds parameter details. Every sentence earns its place with no wasted words, making it easy for an AI agent to parse quickly.

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 an output schema (which handles return values), no annotations, and low complexity (one optional parameter), the description is minimally adequate. It covers the purpose and parameter meaning but lacks behavioral context like error handling or performance hints. It's complete enough for basic use but could be improved with more 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 description adds meaningful context for the single parameter: it explains that platform_id filters by platform and specifies '0 = all', which clarifies the default behavior. Since schema description coverage is 0% and there's only one parameter, this effectively compensates, providing essential semantics beyond the bare schema.

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: 'List BIOS/firmware files' specifies the verb (list) and resource (BIOS/firmware files). It distinguishes from siblings like romm_platforms (which likely lists platforms) and romm_search (which searches). However, it doesn't explicitly differentiate from romm_library_items or romm_collections, which might also list items, so it's not a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning optional filtering by platform, but it doesn't provide explicit guidance on when to use this tool versus alternatives like romm_search or romm_library_items. There's no mention of prerequisites, exclusions, or specific scenarios where this tool is preferred over others in the sibling list.

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