Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_role_privileges

Read-onlyIdempotent

Retrieves bounded direct native privilege IDs and depth masks for a Dataverse security role, without inferring effective user or record access.

Instructions

Read bounded direct native privilege IDs and depth masks for a security role. Does not infer effective user or record access.

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": {
      "role_id": "<role_id>"
    },
    "name": "list_role_privileges"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
role_idYes
max_pagesNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful scope with 'direct native' and 'does not infer effective' access, but it does not explain pagination behavior, limits beyond 'bounded,' or any authorization requirements.

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?

Two tightly written sentences with no wasted wording. The core operation is front-loaded, and the exclusion is stated immediately after.

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?

The description names the returned content—privilege IDs and depth masks—which helps because there is no output schema. However, for a four-parameter security listing tool, it leaves important operational details such as pagination semantics and parameter meanings unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, and the description does not clarify role_id, top, or max_pages. 'Bounded' vaguely hints at limiting results but does not explain how top and max_pages control pagination, so it fails to compensate for the low schema coverage.

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 states a specific read operation and resource: direct native privilege IDs and depth masks for a security role. It also distinguishes the result from effective user or record access, which separates it from security-context and record-access siblings at a glance.

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

Usage Guidelines4/5

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

It gives a clear usage boundary by saying it does not infer effective user or record access, so an agent knows this is for raw direct role privileges. It does not explicitly name change_role_privilege or manage_security_role as the alternatives for mutation, leaving some routing inference to the agent.

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