dataverse-mcp-server

delete_record

Delete a record from a Dataverse table by entity set and record GUID; currently disabled for safety.

Instructions

Delete a record from a Dataverse table (currently disabled for safety)

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Record GUID
`entity_set`	Yes	Entity set name

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Oct 3, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.5.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: the operation is disabled for safety. Beyond that it is silent on permission requirements, reversibility, and the failure mode an agent will actually observe when calling it, leaving meaningful gaps for a destructive operation.

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?

A single compact sentence with the operation front-loaded and the critical disabled status attached inline. It is not padded, though the parenthetical could have been a clearly separated clause for faster scanning.

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

Completeness3/5

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

For a destructive two-parameter tool with no annotations and no output schema, the description covers the core fact (disabled) but omits permission requirements, expected error behavior, and any alternative path. It is minimally adequate rather than complete.

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

Parameters3/5

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

Schema description coverage is 100% (id as Record GUID, entity_set as Entity set name), so the schema already fully documents both parameters. The description adds no syntax, format, or constraint information beyond the schema, matching the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Delete a record from a Dataverse table"), making the operation immediately identifiable and distinguishing it from record-mutation siblings like create_record/update_record. It does not explicitly contrast against adjacent delete tools such as delete_attribute, so it stops short of a 5.

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 parenthetical "currently disabled for safety" implicitly signals the tool should not be invoked, which is a usable constraint. However, there is no explicit when-to-use guidance, no routing to alternatives for retiring data, and no statement of what the agent should do instead.

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