Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_plugin_steps

Retrieve registered plugin steps in Dynamics CRM, optionally filtered by entity or plugin type, to manage and audit custom business logic execution.

Instructions

Lista os steps registrados para plugins, opcionalmente filtrados por entidade

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityLogicalNameNoFiltrar por entidade
pluginTypeIdNoFiltrar por tipo de plugin

Implementation Reference

  • The implementation of the 'dynamics_list_plugin_steps' tool handler, which lists registered plugin steps in Dataverse with optional filters.
    server.tool(
      "dynamics_list_plugin_steps",
      "Lista os steps registrados para plugins, opcionalmente filtrados por entidade",
      z.object({
        entityLogicalName: z.string().optional().describe("Filtrar por entidade"),
        pluginTypeId: z.string().optional().describe("Filtrar por tipo de plugin"),
      }).shape,
      async (params: { entityLogicalName?: string; pluginTypeId?: string }) => {
        const filters: string[] = [];
        if (params.entityLogicalName) {
          filters.push(`configuration eq '${params.entityLogicalName}' or sdkmessagefilterid/primaryobjecttypecode eq '${params.entityLogicalName}'`);
        }
        if (params.pluginTypeId) {
          filters.push(`_plugintypeid_value eq '${params.pluginTypeId}'`);
        }
    
        const result = await client.list("sdkmessageprocessingsteps", {
          select: [
            "sdkmessageprocessingstepid", "name", "stage", "mode",
            "rank", "statecode", "filteringattributes", "description",
            "_sdkmessageid_value", "_plugintypeid_value",
          ],
          filter: filters.length > 0 ? filters.join(" and ") : undefined,
          orderby: "name asc",
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Steps encontrados: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
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 it's a list operation, implying read-only behavior, but doesn't specify whether it returns all steps or is paginated, what authentication or permissions are required, or any rate limits. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 tool's purpose and optional filtering. It's front-loaded with the main action and resource, with no redundant or unnecessary information, making it highly concise and well-structured.

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?

Given the tool's complexity (a list operation with optional filtering), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and hints at parameters but lacks details on behavior, output format, or usage context. For a tool in this context, it should provide more guidance on what the list includes and how to interpret results.

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 description mentions optional filtering by entity, which corresponds to the 'entityLogicalName' parameter, adding context beyond the schema's description of 'Filtrar por entidade'. However, with 100% schema description coverage, the schema already documents both parameters adequately. The description doesn't add significant semantic value for the 'pluginTypeId' parameter or clarify parameter interactions, so a baseline score of 3 is appropriate.

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 action ('Lista os steps registrados') and resource ('para plugins'), making the purpose understandable. It specifies optional filtering by entity, which adds specificity. However, it doesn't explicitly distinguish this tool from sibling tools like 'dynamics_list_plugin_types' or 'dynamics_list_plugin_assemblies', which also list plugin-related items.

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 mentions optional filtering by entity, implying usage when filtering is needed, but provides no explicit guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when-not-to-use scenarios, or comparisons to sibling tools like 'dynamics_get_plugin_performance' or 'dynamics_get_plugin_trace_logs' that might overlap in context.

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