romm-mcp

Overview Schema Source Related Servers Discussions Admin

add_roms_to_collection

Add selected ROM IDs to an existing collection by specifying the collection ID and ROM IDs, enabling direct library organization.

Instructions

Add ROM IDs to an existing collection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection_id": "<collection_id>",
      "rom_ids": "<rom_ids>"
    },
    "name": "add_roms_to_collection"
  }
}

Input Schema

Name	Required	Description	Default
`rom_ids`	Yes
`collection_id`	Yes

Output Schema

Name	Required	Description	Default
`ok`	No
`action`	Yes
`rom_ids`	No
`resource_id`	No
`collection_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already signal that this is a non-read-only, non-destructive, non-idempotent operation. The description adds the precondition that the target collection must already exist, but it does not disclose behaviors such as duplicate handling, whether ROMs are appended, or what happens if any ROM ID is invalid. It does not contradict the annotations.

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 one short, front-loaded sentence containing no filler or repetition. Every word contributes to the core meaning, and it is appropriately sized for a simple two-parameter operation.

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?

For a low-complexity tool with two required parameters and an output schema, the description is mostly adequate: it states the operation and the existing-collection precondition. It lacks any guidance on when not to use it or what happens in edge cases, but the output schema and annotations cover some of the missing context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate for missing parameter details. It maps the two parameters well: 'ROM IDs' to rom_ids and 'existing collection' to collection_id, adding meaning to collection_id beyond the bare title. It does not elaborate on constraints or behavior, but the parameter names and schema types are already fairly self-explianatory.

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?

The description states a specific verb and resource: it adds ROM IDs to an existing collection. This clearly distinguishes it from sibling tools like remove_roms_from_collection and create_collection because it specifies 'add' and 'existing collection'.

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 phrase 'existing collection' implies the intended use case: the collection must already exist, so creating a collection would be a different tool. However, it does not explicitly name alternatives or state when this tool should be chosen over related siblings.

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