Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_toggle_plugin_step

Activate or deactivate a plugin step in Microsoft Dynamics CRM by specifying the step ID and desired state to control workflow execution.

Instructions

Ativa ou desativa um step de plugin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepIdYesID do step do plugin
enabledYestrue para ativar, false para desativar

Implementation Reference

  • The implementation of the 'dynamics_toggle_plugin_step' tool, which updates the statecode and statuscode of a plugin step in Dynamics.
    server.tool(
      "dynamics_toggle_plugin_step",
      "Ativa ou desativa um step de plugin",
      EnableDisablePluginStepSchema.shape,
      async (params: z.infer<typeof EnableDisablePluginStepSchema>) => {
        await client.update("sdkmessageprocessingsteps", params.stepId, {
          statecode: params.enabled ? 0 : 1,
          statuscode: params.enabled ? 1 : 2,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Step ${params.stepId} ${params.enabled ? "ativado" : "desativado"} com sucesso!`,
            },
          ],
        };
  • The input schema definition for the 'dynamics_toggle_plugin_step' tool.
    export const EnableDisablePluginStepSchema = z.object({
      stepId: z.string().describe("ID do step do plugin"),
      enabled: z.boolean().describe("true para ativar, false para desativar"),
    });
Behavior2/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 states the tool 'activates or deactivates' a plugin step, which implies mutation but doesn't disclose behavioral traits like permission requirements, whether this is reversible, side effects, or what happens to the step's state. For a mutation tool with zero annotation coverage, this is inadequate.

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, efficient sentence in Portuguese that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'activating' or 'deactivating' entails, potential side effects, error conditions, or what the tool returns. For a tool that modifies system state, more context 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?

Schema description coverage is 100%, with both parameters clearly documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain what a 'stepId' represents or provide context for the 'enabled' parameter). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('ativa ou desativa' - activates or deactivates) and the resource ('um step de plugin' - a plugin step). It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'dynamics_delete_plugin_step' or 'dynamics_register_plugin_step'.

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. There are related sibling tools like 'dynamics_delete_plugin_step' and 'dynamics_register_plugin_step', but the description doesn't mention when to choose toggle versus delete/register, nor does it specify any prerequisites or context for usage.

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