Skip to main content
Glama
Sign In
mcp-romm

mcp-romm

by lodordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

romm_add_to_collection

Append one or more ROMs to an existing collection using collection and ROM IDs, preserving the current list.

Instructions

Add one or more ROMs to a collection (without replacing the existing list).

collection_id: The collection's ID (from romm_collections). rom_ids: List of ROM IDs to add.

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": "romm_add_to_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_idYes
rom_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

Discloses that the operation is additive (does not replace), which is key behavioral information. Lacks details on preconditions (e.g., does collection need to exist?) or error conditions. Without annotations, the description carries the full burden but leaves some gaps.

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 succinct sentences with inline parameter explanations. No extraneous content, front-loaded with the verb and action.

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?

Covers the essential purpose and parameters. With an output schema present, return value details are not needed. Could be improved by mentioning that collections must exist or that the operation is atomic, but overall adequate for a simple additive tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains both parameters: collection_id is sourced from romm_collections, and rom_ids are a list of ROM IDs. This adds all necessary meaning beyond the raw schema.

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 it adds ROMs to a collection without replacing, which distinguishes it from setting or removing. The sibling tool romm_remove_from_collection is the obvious counterpart, and the description explicitly notes the additive behavior.

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

Usage Guidelines4/5

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

Provides clear context for when to use (to add ROMs to a collection) and hints that it does not replace the existing list. However, does not explicitly mention when not to use or suggest the removal sibling.

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