Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_record_by_id

Retrieve a single Dynamics 365 record by GUID and optionally select specific attributes, so you can inspect exact record details without querying the full collection.

Instructions

Retrieve detailed information for a single record by its GUID.

Input Schema

NameRequiredDescriptionDefault
idYesThe GUID of the record
selectNoComma-separated list of attributes to retrieve
collectionNameNoCompatibility alias for collection_name; conflicting values are rejected.
collection_nameNoLogical collection name
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

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 behavioral burden, yet it discloses nothing about permissions, not-found behavior, rate limits, or return shape. "Retrieve" weakly implies a read-only operation, but a caller cannot confirm safety or failure modes from this text.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the missing guidance rather than a deliberate trade-off.

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 five-parameter read tool with no output schema, the definition is only minimally complete: it never mentions that a collection name (or its alias) must accompany the id, which is a real invocation precondition enforced by the schema's anyOf. A caller reading only the description could attempt the call with just an id and fail.

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%, so all five parameters (id, select, collection_name/collectionName alias, environment_profile) are already documented inline. The description only echoes the GUID concept and adds no semantics such as select projection behavior or the alias conflict rule, so baseline 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 gives a specific verb and resource ("Retrieve detailed information for a single record") plus the lookup key (GUID), which separates it from bulk/query siblings like search_records_by_odata and query_by_fetchxml. It stops short of naming those siblings explicitly, but the single-record-by-id scope is 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?

There is no when-to-use guidance, no mention of alternatives (e.g., search_records_by_odata when only non-key fields are known, query_by_fetchxml for multi-record reads), and no prerequisites. The agent must infer routing from the tool name alone.

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