Skip to main content
Glama
rededis

dataverse-mcp-server

by rededis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_entity

Create a new Dataverse table with specified columns and attributes. Define logical names, data types, and ownership settings for your environment.

Instructions

Create a new Dataverse table (entity) with specified attributes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attributesNoAdditional attributes to create with the entity
descriptionNoTable description
display_nameYesDisplay name
logical_nameYesLogical name with publisher prefix (e.g. 'contoso_newtable')
ownership_typeNoOwnership type (default: UserOwned)
primary_attribute_nameNoLogical name for primary name attribute (default: '{prefix}_name')
display_collection_nameYesPlural display name
primary_attribute_display_nameNoDisplay name for primary name attribute (default: 'Name')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.7.1
    • 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."
  3. First observedv0.5.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely fails: it does not state that this is an irreversible schema mutation, whether it requires specific privileges or an unmanaged solution context, whether the entity and its attributes are created atomically, or what happens on partial failure. Only the bare act of creation is conveyed.

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 or repetition. It is efficient, though arguably terse to the point of under-specification rather than over-specification.

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 high-impact schema-mutation tool with no annotations, no output schema, and eight parameters including a nested attribute list, the description is too thin. An agent would want to know about irreversibility, solution/publisher scoping, and creation semantics, none of which are covered.

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%, so parameters like logical_name, ownership_type, and the nested attribute definitions are already documented in the schema; baseline 3 applies. The phrase 'with specified attributes' nods at the attributes array but adds no meaning beyond the schema's own descriptions and defaults.

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 gives a specific verb and resource ('Create a new Dataverse table (entity)'), and the parenthetical distinguishes entity from its siblings like create_record, add_attribute, and delete_entity. It stops short of explicitly naming an alternative tool, so it is clear but not fully sibling-differentiating.

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?

There is no guidance on when to use this tool versus add_attribute, create_record, or create_relationship, nor any prerequisite (e.g., that a publisher prefix and target solution context are needed). The agent must infer usage entirely from the name and schema.

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