dataverse-mcp-server

invoke_action

Invoke Dataverse Web API actions (POST), bound or unbound, for non-CRUD operations such as PublishDuplicateRule or QualifyLead. Pass entity set and record ID for bound actions; omit both for unbound.

Instructions

Invoke a Dataverse Web API action (POST) — bound or unbound. Use for operations that are not plain CRUD, e.g. PublishDuplicateRule (bound to a duplicaterule) or QualifyLead (bound to a lead), or UnpublishDuplicateRule (unbound, takes DuplicateRuleId). Whether an action is bound is defined in the Web API $metadata. Pass entity_set+id for bound actions, neither for unbound. parameters becomes the JSON request body.

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": {
      "name": "<name>"
    },
    "name": "invoke_action"
  }
}

Input Schema

Name	Required	Description
`id`	No	Record GUID the bound action targets. Required iff entity_set is set.
`name`	Yes	Action name, e.g. 'PublishDuplicateRule', 'QualifyLead'. The Microsoft.Dynamics.CRM. namespace is added for bound calls and may be omitted.
`entity_set`	No	Entity set (plural, e.g. 'leads') for a bound action. Omit for unbound actions.
`parameters`	No	Action parameters sent as the JSON request body (e.g. { DuplicateRuleId } for PublishDuplicateRule, { CreateAccount, CreateContact, Status } for QualifyLead).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.1Nov 5, 2026

changedInput schema / properties / name / description

Previous value: -"Action name, e.g. 'PublishDuplicateRule', 'QualifyLead'. Bare names are namespaced automatically for bound calls; pass a fully-qualified name to override."New value: +"Action name, e.g. 'PublishDuplicateRule', 'QualifyLead'. The Microsoft.Dynamics.CRM. namespace is added for bound calls and may be omitted."

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

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a lot: it is a POST mutation, boundness is determined by the Web API $metadata rather than guessed, and parameters become the JSON request body. It omits side-effect/reversibility warnings (e.g. QualifyLead creates records) and any error or permission behavior, which matters for a mutation tool.

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?

Four dense sentences, front-loaded with the operation type, then the when-to-use rationale, then the boundness rule, then the body mapping. No filler and no repetition of the schema verbatim.

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 4-parameter mutation tool with no annotations and no output schema, the invocation mechanics are well covered, but nothing is said about the response shape (there is no output schema to fall back on) or about the side effects an agent should expect. Those gaps are the main reason this is adequate rather than complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description still adds conceptual meaning by explaining why entity_set and id are coupled (bound vs unbound action definitions in $metadata) and by noting the Microsoft.Dynamics.CRM. namespace can be omitted, rather than just restating the field descriptions.

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 ('Invoke a Dataverse Web API action (POST)') and scopes it against CRUD siblings by saying it is for 'operations that are not plain CRUD'. The closest alternative, the sibling invoke_function, is never named, so the action-vs-function choice is left to the agent's Dataverse knowledge.

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?

Gives clear conditions for use ('not plain CRUD') with three concrete examples, and states the routing rule for bound ('Pass entity_set+id') versus unbound ('neither') calls. It stops short of explicit exclusions or pointing to invoke_function when the target is actually a function.

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