PowerPlatform MCP Server

get-entity-metadata

Retrieve metadata for any PowerPlatform entity by providing its logical name. Understand entity fields, attributes, and relationships to build accurate OData queries.

Instructions

Get metadata about 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-metadata"
  }
}

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

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read operation but does not state side effects, return format, or any operational constraints. The absence of detail leaves the agent uncertain about what 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.

Conciseness4/5

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

The description is a single, direct sentence without fluff. It is efficient, but the brevity contributes to under-specification, preventing a higher score.

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?

Given no output schema, no annotations, and a single parameter, the description is too minimal to be complete. It does not explain what metadata is returned, how it relates to sibling tools, or any usage notes that would help an agent invoke it correctly.

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 schema fully describes 'entityName' (100% coverage). The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 states the verb and resource: 'Get metadata about a PowerPlatform entity'. This is clear and specific. However, it does not differentiate from sibling tools like get-entity-attributes or get-entity-relationships, which are also about entity metadata.

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 on when to use this tool vs alternatives. The description only says 'Get metadata', without specifying scenarios, prerequisites, or exclusions. Sibling tools are more specific, but no comparison is made.

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

Deploy Server