Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_solution_components

List components within a Dynamics CRM solution to manage schema, track dependencies, and facilitate deployment workflows.

Instructions

Lista componentes de uma solução

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solutionUniqueNameYesNome único da solução
componentTypeNoFiltrar por tipo de componente

Implementation Reference

  • The handler for dynamics_list_solution_components. It fetches the solution ID first and then lists the components associated with that solution.
    server.tool(
      "dynamics_list_solution_components",
      "Lista componentes de uma solução",
      ListSolutionComponentsSchema.shape,
      async (params: z.infer<typeof ListSolutionComponentsSchema>) => {
        // Get solution ID first
        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;
        let filter = `_solutionid_value eq '${solutionId}'`;
        if (params.componentType !== undefined) {
          filter += ` and componenttype eq ${params.componentType}`;
        }
    
        const result = await client.list("solutioncomponents", {
          select: ["solutioncomponentid", "componenttype", "objectid", "rootcomponentbehavior", "ismetadata"],
          filter,
          orderby: "componenttype asc",
        });
    
        const components = result.value.map((c: Record<string, unknown>) => ({
          ...c,
          componentTypeName: COMPONENT_TYPE_NAMES[c.componenttype as number] || `Unknown (${c.componenttype})`,
        }));
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Componentes em ${params.solutionUniqueName}: ${components.length}\n\n${JSON.stringify(components, null, 2)}`,
            },
          ],
        };
      }
    );
  • Input validation schema for dynamics_list_solution_components.
    export const ListSolutionComponentsSchema = z.object({
      solutionUniqueName: z.string().describe("Nome único da solução"),
      componentType: z.number().optional().describe("Filtrar por tipo de componente"),
    });
  • Registration of the tool in the server.tool call.
    "dynamics_list_solution_components",
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 lists components but doesn't disclose behavioral traits such as whether it's read-only, pagination behavior, rate limits, authentication needs, or what happens if the solution doesn't exist. This leaves significant gaps in understanding how the tool operates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 purpose. It's front-loaded and wastes no words, though it could benefit from more detail. However, given its brevity and clarity, it scores well for conciseness.

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 a list operation with potential complexity (e.g., filtering, pagination), the description is incomplete. It doesn't cover return values, error conditions, or behavioral aspects, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 both parameters ('solutionUniqueName' and 'componentType'). The description doesn't add any meaning beyond this, such as explaining what 'componentType' values represent or providing examples. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Lista componentes de uma solução' clearly states the action (list) and target (solution components) in Portuguese, which translates to 'List components of a solution'. It's specific about the resource but doesn't distinguish from sibling tools like 'dynamics_list_solutions' or 'dynamics_list_columns', making it somewhat vague in context.

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 on when to use this tool versus alternatives. For example, it doesn't specify if this is for enumerating all components or filtered ones, or how it differs from other list tools like 'dynamics_list_tables' or 'dynamics_list_web_resources'. The description lacks context for selection among siblings.

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