ragic-mcp

ragic_delete_record

Delete a single record from a Ragic form using its path, sheet index, and record ID.

Instructions

Delete a record. Ragic does not support batch delete via this endpoint.

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": {
      "path": "<path>",
      "sheet_index": "<sheet_index>",
      "record_id": "<record_id>"
    },
    "name": "ragic_delete_record"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`record_id`	Yes
`sheet_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description should disclose behavioral traits. It identifies the action as destructive but does not mention authentication needs, reversibility, error behavior, or success/failure responses. The no-batch note is helpful but insufficient.

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?

The description is very concise with two sentences, front-loading the primary action. However, it may be too brief given the lack of parameter explanations and usage context.

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

Completeness2/5

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

For a delete operation with three required parameters and no output schema or annotations, the description is incomplete. It fails to clarify parameter roles, return values, or error conditions, leaving significant gaps for an agent.

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

Parameters1/5

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

The description offers no explanation for the three required parameters (path, record_id, sheet_index). Since schema description coverage is 0%, the description should compensate, but it adds no meaning beyond the parameter names.

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 'Delete a record' with a specific verb and resource, and distinguishes from siblings like ragic_create_record and ragic_update_record. The additional note about batch delete adds clarity.

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 mentions that batch delete is not supported, implying when not to use this tool. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide contexts such as prerequisites or side effects.

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

Deploy Server