Skip to main content
Glama
Sign In
mcp-romm

mcp-romm

by lodordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

romm_delete_collection

Permanently delete a collection from RomM. Only removes the grouping, not the underlying ROMs. Provide the collection ID.

Instructions

Permanently delete a collection. This cannot be undone.

The ROMs themselves are not deleted — only the collection grouping.

collection_id: The collection's ID (from romm_collections).

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>"
    },
    "name": "romm_delete_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses destructive permanent action with no confirmation. Clarifies that only the grouping is deleted, ROMs remain. No annotations present, so description carries full burden and meets it well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: main action, effect, parameter explanation. Front-loaded with purpose. Efficient, though could reorder to put parameter last.

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 all essential aspects for a simple delete operation: purpose, irreversibility, effect on ROMs, parameter. Output schema exists, so no need to describe return values.

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?

The only parameter collection_id is explicitly explained with its source ('from romm_collections'). Schema has 0% description coverage, so description fully compensates.

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?

Clear verb+resource combination: 'Permanently delete a collection.' Distinguishes from siblings like romm_remove_from_collection which removes ROMs but not the collection.

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?

Explicitly states irreversibility ('cannot be undone') and what happens to ROMs ('not deleted'). Implicity suggests using alternative tools if you want to keep the collection or only remove ROMs.

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