PowerPlatform MCP Server

use-powerplatform-prompt

Generate structured prompts for Dataverse entity overview, attribute details, OData queries, and relationship maps. Provide an entity name and prompt type to receive a tailored template.

Instructions

Use a predefined prompt template for PowerPlatform entities

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": {
      "promptType": "<promptType>",
      "entityName": "<entityName>"
    },
    "name": "use-powerplatform-prompt"
  }
}

Input Schema

Name	Required	Description
`entityName`	Yes	The logical name of the entity
`promptType`	Yes	The type of prompt template to use
`attributeName`	No	The logical name of the attribute (required for ATTRIBUTE_DETAILS prompt)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.5Jul 31, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the tool is read-only, deterministic, requires authentication, or has side effects. The single sentence conveys purpose only, with no insight into how the operation behaves or what output to expect.

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?

The description is a single, direct sentence with no redundant words. It is appropriately sized for a simple purpose statement and front-loads the verb.

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?

With three parameters, no output schema, and no annotations, the description fails to explain what the tool returns, how promptType and attributeName interact, or what the entity name should reference. It is too sparse to be contextually complete for an agent to invoke correctly without further information.

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%, with each parameter already documented. The description adds no additional parameter context beyond the schema, so the baseline score of 3 applies.

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 uses a clear verb ('Use') and resource ('predefined prompt template for PowerPlatform entities'), distinguishing it from sibling tools that all retrieve metadata or records. However, it does not specify what 'using' produces (e.g., a generated prompt string), so it lacks full clarity about the tool's output.

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 guidance is provided on when to use this tool instead of the sibling tools. There is no mention of specific use cases, prerequisites, or exclusions. The description is purely declarative and gives no contextual direction.

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

Deploy Server