Skip to main content
Glama
Sign In
PowerPlatform MCP Server

PowerPlatform MCP Server

by dayour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get-record

Retrieve a specific record from a Power Platform/Dataverse entity by providing the plural entity name and the record's GUID.

Instructions

Get a specific record by entity name (plural) and ID

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": {
      "entityNamePlural": "<entityNamePlural>",
      "recordId": "<recordId>"
    },
    "name": "get-record"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYesThe GUID of the record
entityNamePluralYesThe plural name of the entity (e.g., 'accounts', 'contacts')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.5

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic 'get' action and does not disclose behavior for missing records, authorization requirements, or response details. The only extra detail (entity name must be plural) is already present in the schema.

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 sentence that immediately conveys the core purpose and required inputs. It is concise, front-loaded, and contains no extraneous information.

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 two-parameter get tool, the description is minimally adequate but has clear gaps: it does not describe the return format or error behavior, and there is no output schema to compensate.

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 coverage is 100% for both parameters, with clear descriptions for entityNamePlural and recordId. The tool description adds no new meaning beyond restating these identifiers, so the baseline 3 is appropriate.

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 clearly states the tool's function: retrieving a specific record by entity name (plural) and ID. This distinguishes it from sibling tools like query-records (which lists records) and get-entity-metadata (which retrieves metadata).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching a single known record by ID, but it does not explicitly mention when to use this tool versus alternatives like query-records. There is no when-not-to-use or alternative guidance.

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