Skip to main content
Glama

romm_stats

Retrieve library statistics including platform counts, ROM totals, save files, and storage usage for game collection management.

Instructions

Get library statistics — platform count, ROM count, saves, total size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `romm_stats` function is decorated with `@mcp.tool()` and implements the logic to fetch and format statistics from the RomM API's `/stats` endpoint.
    async def romm_stats() -> str:
        """Get library statistics — platform count, ROM count, saves, total size."""
        data = await _get("stats")
    
        if not isinstance(data, dict):
            return "No stats available."
    
        lines = ["RomM Library Statistics:\n"]
        lines.append(f"  Platforms: {data.get('PLATFORMS', 0)}")
        lines.append(f"  ROMs: {data.get('ROMS', 0)}")
        lines.append(f"  Saves: {data.get('SAVES', 0)}")
        lines.append(f"  Save states: {data.get('STATES', 0)}")
        lines.append(f"  Screenshots: {data.get('SCREENSHOTS', 0)}")
        total = data.get("TOTAL_FILESIZE_BYTES", 0)
        if total:
            lines.append(f"  Total size: {_fmt_size(total)}")
    
        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 of behavioral disclosure. It states the tool 'Get's statistics, implying a read-only operation, but does not specify any behavioral traits such as permissions required, rate limits, or response format. The description lacks details on what 'library' refers to or how the statistics are computed, leaving gaps in transparency.

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 that front-loads the key action ('Get library statistics') and lists specific metrics without any wasted words. It is appropriately sized for a tool with no parameters and clear output focus.

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, an output schema exists, and no annotations are provided, the description is minimally complete. It states what the tool does but lacks context on library scope, data freshness, or how it differs from siblings. The output schema may cover return values, but the description could better integrate with the tool's role in the server ecosystem.

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, and the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, as there are no parameters to document. It appropriately focuses on the tool's purpose without unnecessary parameter details.

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 with the verb 'Get' and specifies the resource 'library statistics', listing concrete metrics like platform count, ROM count, saves, and total size. However, it does not explicitly differentiate from sibling tools (e.g., romm_status or romm_library_items), which might also provide related statistical or library information.

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 no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context for usage, or comparisons to sibling tools like romm_status or romm_library_items, leaving the agent to infer usage based on the tool name and description alone.

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