Skip to main content
Glama
Sign In
mcp-romm

mcp-romm

by lodordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

romm_scan_library

Trigger a library rescan to discover newly added ROMs and platforms. The scan runs as a background task and returns immediately.

Instructions

Trigger a library rescan to discover new ROMs and platforms.

This is a background task — it returns immediately. New ROMs will appear in the library as the scan progresses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "romm_scan_library"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses that it is a background task, returns immediately, and that new ROMs will appear as the scan progresses. Without annotations, this provides good behavioral context, though it could mention any potential side effects.

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?

Two sentences, front-loaded with key information, no wasted words. Efficient and clear.

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 zero parameters and no output schema details in the description, the description covers the essential behavior. However, since an output schema exists, the description could briefly mention what the tool returns (e.g., a task ID).

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?

No parameters exist, and schema coverage is 100%. No additional parameter info is needed. Baseline 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'Trigger' and the resource 'library rescan', and explains the purpose: discover new ROMs and platforms. Distinguishes itself from siblings as there is no other scan tool.

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?

Implies usage when wanting to discover new ROMs, but does not provide explicit when-not or alternative tools for similar tasks. Lacks guidance on prerequisites or frequency.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools