Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_delete_solution

Remove unmanaged solutions from Dynamics CRM to clean up development environments and manage solution lifecycle.

Instructions

Remove uma solução unmanaged do Dynamics CRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solutionUniqueNameYesNome único da solução a remover

Implementation Reference

  • The handler for 'dynamics_delete_solution' which finds the solution ID by unique name and then calls the client to remove it.
    server.tool(
      "dynamics_delete_solution",
      "Remove uma solução unmanaged do Dynamics CRM",
      DeleteSolutionSchema.shape,
      async (params: z.infer<typeof DeleteSolutionSchema>) => {
        const solutions = await client.list("solutions", {
          select: ["solutionid"],
          filter: `uniquename eq '${params.solutionUniqueName}'`,
          top: 1,
        });
    
        if (solutions.value.length === 0) {
          return {
            content: [{ type: "text" as const, text: `Solução '${params.solutionUniqueName}' não encontrada.` }],
          };
        }
    
        const solutionId = (solutions.value[0] as Record<string, unknown>).solutionid as string;
        await client.remove("solutions", solutionId);
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Solução ${params.solutionUniqueName} removida com sucesso!`,
            },
          ],
        };
      }
  • The Zod schema definition for the inputs of the delete solution tool.
    export const DeleteSolutionSchema = z.object({
      solutionUniqueName: z.string().describe("Nome único da solução a remover"),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive operation, the description doesn't specify whether this is reversible, what permissions are required, whether it affects dependent components, or what happens to the solution data. For a deletion tool with zero annotation coverage, this leaves critical behavioral aspects undocumented.

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 with zero wasted words. It's appropriately sized for a single-parameter tool and gets straight to the point without unnecessary elaboration.

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?

For a destructive deletion tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'unmanaged' means in this context, what the consequences of deletion are, whether there are dependencies to check first, or what confirmation/response to expect. Given the complexity and risk of a deletion operation, more contextual 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?

Schema description coverage is 100%, so the schema already documents the single parameter 'solutionUniqueName' with its description. The tool description adds no additional parameter information beyond what's in the schema, meeting the baseline expectation but not providing extra value.

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 ('Remove') and target resource ('uma solução unmanaged do Dynamics CRM'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'dynamics_remove_solution_component' or 'dynamics_delete_column', which reduces clarity about scope boundaries.

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?

No guidance is provided about when to use this tool versus alternatives like 'dynamics_remove_solution_component' or 'dynamics_delete_solution' versus other deletion tools. The description lacks context about prerequisites, consequences, or appropriate scenarios for this specific deletion operation.

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