Skip to main content
Glama
Sign In
PowerPlatform MCP Server

PowerPlatform MCP Server

by dayour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-entity-attribute

Retrieve metadata for a specific attribute of a PowerPlatform entity, providing the logical field definition for use in queries and integrations.

Instructions

Get a specific attribute/field 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>",
      "attributeName": "<attributeName>"
    },
    "name": "get-entity-attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityNameYesThe logical name of the entity
attributeNameYesThe logical name of the attribute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.5

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It only states 'Get', which implies a read operation, but does not clarify whether it returns attribute metadata or a value, nor any permissions or return format. This leaves significant ambiguity.

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 states the tool's core purpose with no wasted words. It is appropriately sized for a simple getter.

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 full schema coverage and no output schema, the description is minimally viable but lacks usage context and clarity on return semantics, which could confuse an agent trying to select between this and related entity tools.

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 already fully documents both parameters (entityName and attributeName) with logical name descriptions. The description adds no additional parameter meaning beyond the schema, so the baseline of 3 applies.

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 uses the verb 'Get' and specifies the resource as 'a specific attribute/field of a PowerPlatform entity', clearly distinguishing it from siblings like get-entity-attributes (plural) and get-record. It is specific and unambiguous.

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 versus alternatives such as get-entity-attributes or get-record. The description lacks any contextual instructions or exclusions.

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