Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

dynamics_get_slow_plugins

Identify slow-performing plugins in Microsoft Dynamics CRM to improve system performance by analyzing execution times and pinpointing bottlenecks.

Instructions

Identifica plugins que estão tornando o sistema lento

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
minDurationMsNoDuração mínima em ms

Implementation Reference

  • src/tools/telemetry/index.ts:365-376 (handler)
    The handler function for dynamics_get_slow_plugins which queries Dynamics plugintracelogs to identify slow plugins.
    async (params: z.infer<typeof GetSlowQueriesSchema>) => {
  const result = await client.list("plugintracelogs", {
    select: [
      "typename", "messagename", "primaryentity",
      "performanceexecutionstarttime", "performanceexecutionduration",
      "exceptiondetails", "depth", "createdon",
    ],
    filter: `performanceexecutionduration ge ${params.minDurationMs}`,
    orderby: "performanceexecutionduration desc",
    top: params.top,
  });
  • src/tools/telemetry/index.ts:361-364 (registration)
    Registration of the dynamics_get_slow_plugins tool in the MCP server.
    server.tool(
  "dynamics_get_slow_plugins",
  "Identifica plugins que estão tornando o sistema lento",
  GetSlowQueriesSchema.shape,

Tool Definition Quality

C2.9/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 of behavioral disclosure. It states the tool identifies slow plugins but does not describe how it works (e.g., based on performance metrics, logs), what data it returns (e.g., list of plugins with durations), or any behavioral traits like rate limits, permissions required, or system impact. This is inadequate for a tool with no annotation coverage.

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, clear sentence in Portuguese that efficiently conveys the core purpose without unnecessary words. It is front-loaded and appropriately sized for its content.

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

Completeness2/5

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

Given no annotations, no output schema, and incomplete parameter documentation (50% coverage), the description is insufficient. It lacks details on behavior, output format, and usage context, making it incomplete for effective tool selection and invocation in a complex environment with many sibling tools.

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 50% (one parameter has a description, one does not). The description does not mention any parameters, so it adds no semantic value beyond the schema. The baseline is 3 because the schema provides some documentation, but the description does not compensate for the coverage gap.

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 clearly states the tool's purpose: 'Identifica plugins que estão tornando o sistema lento' (Identifies plugins that are making the system slow). It specifies the verb 'identifica' (identifies) and the resource 'plugins', with the qualifier 'que estão tornando o sistema lento' (that are making the system slow). However, it does not explicitly differentiate from sibling tools like 'dynamics_get_plugin_performance' or 'dynamics_get_plugin_trace_logs', which might have overlapping purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or specific contexts for usage. Given the sibling tools include related performance and plugin tools, this lack of differentiation is a significant gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rafteles2016/mcpDynamics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server