Skip to main content
Glama
Sign In
xrm-mcp

xrm-mcp

by jukkan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ping

Test connectivity to a Microsoft Dataverse environment and verify authentication. Confirm your setup and connection before using other tools.

Instructions

Test connectivity to an XRM/Dataverse environment and verify authentication.

Call this first to verify your setup and connection to the Dataverse environment.

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": {
      "org_url": "<org_url>"
    },
    "name": "ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_urlYesThe Dataverse organization URL (e.g., https://yourorg.crm4.dynamics.com)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It indicates the tool tests connectivity and authentication, implying no destructive side effects. The output schema (context: has output schema) likely details the response, so the description is sufficient.

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 concise sentences with no wasted words. The key purpose and usage advice are front-loaded.

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

Completeness5/5

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

Given the simple single-parameter tool with output schema available, the description fully captures the tool's purpose and recommendation. No additional information is needed.

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 has 100% coverage with a description for 'org_url'. The tool description does not add new semantic info beyond what the schema already provides, so 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 'Test connectivity to an XRM/Dataverse environment and verify authentication,' which is a specific verb+resource. It distinguishes from sibling tools (data manipulation or metadata queries) by focusing on connectivity testing.

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?

The description says 'Call this first to verify your setup,' providing explicit usage context. However, it does not mention when not to use it or alternatives, though its purpose is naturally limited.

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