PowerPlatform MCP Server

get-entity-attributes

Retrieve attributes and fields for a specific PowerPlatform entity by providing its logical name. Simplifies entity metadata exploration for Dataverse.

Instructions

Get attributes/fields of a PowerPlatform entity

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": {
      "entityName": "<entityName>"
    },
    "name": "get-entity-attributes"
  }
}

Input Schema

Name	Required	Description	Default
`entityName`	Yes	The logical name of the entity

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.5Jul 31, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get', which implies read-only, but does not describe what is returned (e.g., field metadata vs. values), pagination, error behavior, or any side effects. This is a thin description for a tool with no structured safety hints.

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, concise sentence that directly communicates the tool's purpose without unnecessary words or repetition. It is well-structured and easy to parse.

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 simple tool with one well-documented parameter, the description is minimally viable but lacks details about the return value or output shape, which is significant since there is no output schema. It does not clarify whether attributes are returned as a list, dictionary, or with specific metadata, so completeness is moderate.

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?

The input schema covers the single parameter 'entityName' with a clear description ('The logical name of the entity'), giving 100% schema coverage. The tool description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the action ('Get') and the resource ('attributes/fields of a PowerPlatform entity'). It distinguishes from the sibling 'get-entity-attribute' by using the plural form, indicating it retrieves multiple attributes rather than a single one. However, it could be more explicit about the scope (e.g., listing all attributes) to fully align with the best examples.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-entity-attribute' or 'get-entity-metadata'. It does not mention scenarios, exclusions, or relationships to sibling tools, leaving the agent to infer usage.

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

Deploy Server