mcp-romm

by lodordev

Overview Schema Source Related Servers Discussions Admin

Python

Remote

romm_delete_note

Permanently delete a note from a ROM. Provide the ROM and note IDs to remove a note irreversibly.

Instructions

Permanently delete a note. This cannot be undone.

rom_id: The ROM's ID. note_id: The note's ID (from romm_rom_notes).

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": {
      "rom_id": "<rom_id>",
      "note_id": "<note_id>"
    },
    "name": "romm_delete_note"
  }
}

Input Schema

Name	Required	Description	Default
`rom_id`	Yes
`note_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jun 23, 2026

TDQS

A4.3/5.0

Behavior4/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. It discloses that deletion is permanent and cannot be undone, which is critical behavioral information. However, it does not mention prerequisites like note existence or authorization requirements.

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 extremely concise with no extraneous text. The purpose is front-loaded, and parameter explanations are efficiently presented in separate lines, making it easy to scan.

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 the presence of an output schema (not shown), the description adequately covers the operation's purpose, parameters, and irreversibility. It could mention error conditions or success indicators, but the core information is sufficient for a deletion 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?

The input schema has 0% description coverage, but the description fully explains both parameters: rom_id as 'The ROM's ID' and note_id as 'The note's ID (from romm_rom_notes)'. This adds essential context beyond the schema's type definitions.

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 clearly states the action 'permanently delete a note' and emphasizes irreversibility. This distinguishes it from sibling tools like romm_add_note and romm_update_note, which serve different purposes.

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 description does not provide explicit guidance on when to use this tool versus its siblings (e.g., add or update). It only implies usage by naming the operation, but lacks exclusions or context for choosing between note-related tools.

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