dataverse-mcp-server

create_entity

Creates a new Dataverse table with specified attributes, enabling you to define custom entities and columns through the MCP server.

Instructions

Create a new Dataverse table (entity) with specified attributes

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": {
      "logical_name": "<logical_name>",
      "display_name": "<display_name>",
      "display_collection_name": "<display_collection_name>"
    },
    "name": "create_entity"
  }
}

Input Schema

Name	Required	Description
`has_notes`	No	Enable notes and attachments on the table (default: false). Cannot be turned off once enabled.
`attributes`	No	Additional attributes to create with the entity
`description`	No	Table description
`display_name`	Yes	Display name
`logical_name`	Yes	Logical name with publisher prefix (e.g. 'contoso_newtable')
`has_activities`	No	Enable activities on the table (default: false). Cannot be turned off once enabled.
`ownership_type`	No	Ownership type (default: UserOwned)
`primary_attribute_name`	No	Logical name for primary name attribute (default: '{prefix}_name')
`display_collection_name`	Yes	Plural display name
`primary_attribute_display_name`	No	Display name for primary name attribute (default: 'Name')

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.9.1Nov 5, 2026

addedInput schema / properties / has_activities

Added value: +{
+  "description": "Enable activities on the table (default: false). Cannot be turned off once enabled.",
+  "type": "boolean"
+}

addedInput schema / properties / has_notes

Added value: +{
+  "description": "Enable notes and attachments on the table (default: false). Cannot be turned off once enabled.",
+  "type": "boolean"
+}

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"

Changed2 schema fields changedv0.7.1Aug 21, 2026

addedInput schema / properties / attributes / items / properties / global_option_set

Added value: +{
+  "description": "Picklist only: bind the column to an existing Global OptionSet by its set name (e.g. 'contoso_sourceset') so the column shares one org-wide list instead of a private copy. Mutually exclusive with options.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / attributes / items / properties / options / description

Previous value: -"Options for Boolean (2 items: false=0, true=1) or Picklist types"New value: +"Options for Boolean (2 items: false=0, true=1) or Picklist types. Creates a Local OptionSet owned by this one column; mutually exclusive with global_option_set."

First observedv0.5.0Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/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 provides almost none. It does not say the operation is irreversible (the schema hints that has_notes/has_activities cannot be disabled once enabled), nor that it mutates org metadata, requires a publisher prefix, or what it returns. Only the one-line purpose is disclosed.

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 front-loaded sentence with no filler. It is efficient, though its brevity is part of why other dimensions are thin rather than a virtue in itself.

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 schema-creating mutation tool with 10 parameters, no annotations, and no output schema, the description omits prerequisites (publisher prefix, target solution), irreversibility of table-level flags, and any post-creation expectations. The schema compensates for parameter detail but not for operational context.

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% and the nested attribute definitions are richly documented, so the baseline is 3. The description's phrase 'with specified attributes' only gestures at the attributes array without adding naming conventions, ordering, or constraints beyond what the schema already states.

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?

States a specific verb and resource — 'Create a new Dataverse table (entity)' — and adds the scope 'with specified attributes', which signals it builds schema, not data. It does not explicitly contrast with siblings like create_record (rows) or add_attribute (extending an existing table), so an agent must infer the distinction from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given: nothing says to use create_record for data, add_attribute for existing tables, or that a publisher/solution context is required. The agent gets no criteria for choosing this tool over the many adjacent siblings in a schema-heavy toolset.

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