Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

create_model_table

Destructive

Creates a custom Dataverse table with a primary text column using native EntityDefinitions, validating solution and publisher prefix; preview by default.

Instructions

Create an ordinary custom table with a primary text name column using native EntityDefinitions. Requires an existing unmanaged solution and matching publisher prefixes. Default preview; does not place fields on forms or request publication.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
dry_runNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
schemaNameNo
descriptionNo
displayNameNo
primaryNameNo
schema_nameNo
display_nameNo
primary_nameNo
ownershipTypeNo
ownership_typeNo
solutionUniqueNameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.
displayCollectionNameNo
display_collection_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a destructive, non-idempotent write, and the description adds meaningful behavior beyond them: dry-run preview is the default, execution requires setting it false, the solution must be unmanaged, and publisher prefixes are validated. It does not warn about duplication or irreversibility of an already-created table, which is the main remaining gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action, then prerequisites, then exclusions. Every clause carries information and there is no filler.

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

Completeness4/5

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

For a 16-parameter mutation with no output schema, the description covers the essential prerequisites, the preview/execute contract, and the return of a native request preview. It is close to complete, but the nested primaryName and display-name array structures remain unexplained beyond the schema.

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 only 31% across 16 parameters, so the description must compensate and it partly does: it explains the meaning of the primary text name column, the solution name requirement and prefix validation, and the preview default. It says nothing about ownershipType, description arrays, or max length constraints, leaving a substantial portion of parameters undocumented.

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 ('Create an ordinary custom table with a primary text name column using native EntityDefinitions') and scopes it to ordinary tables, which distinguishes it from column, relationship, and table-publish siblings in the same family.

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

Usage Guidelines4/5

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

It states concrete prerequisites (existing unmanaged solution, matching publisher prefix) and explicitly says what the tool will not do (no form placement, no publication), which implies that publishing requires a separate call. It does not name the alternative sibling (e.g. publish_model_table) by name, so a point is withheld.

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