Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_api_operation

Read-only

Inspect Dynamics 365 service CSDL metadata to resolve Action/Function overloads, exact parameter types, and binding/import names before invoking an API operation.

Instructions

Read current service CSDL to inspect Action/Function overloads, exact parameter types/facets, binding and import names. Optional entity-set binding narrows signatures. Returns direct input type definitions; nested types are not expanded. Read-only metadata does not prove permissions/runtime support.

Input Schema

NameRequiredDescriptionDefault
bindingNo
actionNameNoExact case-sensitive native operation/import name or qualified name, never a URL/path.
isFunctionNoInvocation defaults false (Action); discovery omits this to inspect both kinds.
action_nameNoExact case-sensitive native operation/import name or qualified name, never a URL/path.
is_functionNoInvocation defaults false (Action); discovery omits this to inspect both kinds.
signatureIdNoAdvertised get_api_operation signature ID; required to disambiguate matching overloads.
signature_idNoAdvertised get_api_operation signature ID; required to disambiguate matching overloads.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and the description is consistent with that. It adds real behavioral context beyond the annotations: it returns direct input type definitions only (nested types are not expanded) and explicitly warns that read-only metadata does not prove permissions or runtime support — a non-obvious limitation that prevents misuse.

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?

Four tight sentences with the core action front-loaded, followed by the binding option, the return-shape caveat, and the permission caveat. No filler, though the final caveat could be folded into the return sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, nested, no-output-schema metadata reader, the description covers purpose, the binding option, what the return contains, and a key limitation. It does not explain how overload disambiguation works end-to-end (when to reach for signatureId), but the schema fills that gap.

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 88%, so the baseline is 3; the schema already explains action_name, isFunction, signatureId and environment_profile. The description only reinforces the binding parameter ("narrows signatures") and adds nothing about overload disambiguation via signatureId, so it does not meaningfully exceed the schema.

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 opens with a specific verb and resource ("Read current service CSDL") and scopes it to inspecting Action/Function overloads, parameter types, binding and import names. That is far more precise than a restated name, though it never names a sibling (e.g. get_entity_metadata_summary or call_d365_api_action) to anchor the boundary.

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?

"Optional entity-set binding narrows signatures" implies when to supply binding, and the closing sentence implies this is a metadata-inspection tool rather than a permission check. However, no explicit when-to-use/when-not or named alternative is given, so an agent must infer routing from the sibling list.

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