Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete record

delete_record
Destructive

Permanently deletes a single record by ID. Blocks deletion when page blocks reference it, listing those pages; set force to true to delete anyway and leave references stale.

Instructions

Permanently delete one record (entry) by its id. A record still used by page blocks is refused and the error lists those pages; force: true deletes it anyway and leaves those references stale.

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": {
      "recordId": "<recordId>"
    },
    "name": "delete_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoDelete even when page blocks still reference the record. Without it, a referenced record is refused and the error names the pages using it.
recordIdYesThe record's id to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "recordId"
      +]
  2. First observedv0.73.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only give destructiveHint=true and readOnlyHint=false; the description goes substantially beyond them by disclosing that deletion is permanent, that a referenced record is refused with an error naming the offending pages, and that force:true leaves those references stale. That is exactly the consequence information an agent needs before an irreversible write.

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 the destructive action and its scope, then the refusal/force behavior. No filler, and the most important safety fact ('Permanently') comes first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with no output schema, the description covers permanence, the default failure mode, the error content, and the risk of the override. Nothing material is left for an agent to infer before calling it.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the positive consequence of force (references are left stale) as opposed to merely bypassing the guard. It does not add anything for recordId beyond what the schema says.

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 ('Permanently delete one record (entry) by its id'), scoping it to a single record so it is distinguishable from bulk deletion siblings by name and behavior. 'Permanently' also signals irreversibility, which is the key selection criterion for a delete operation.

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 explains the conditional path (refused when page blocks reference the record, overridable with force) but never states when an agent should prefer this tool over alternatives such as update_record, bulk_delete_records, or detaching the block first. Usage is implied by the refusal rule rather than an explicit decision guide.

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