Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_solutions

Retrieve installed solutions from Dynamics CRM with filtering options for managed, unmanaged, or specific names to manage deployment workflows.

Instructions

Lista soluções instaladas no Dynamics CRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
managedOnlyNo
unmanagedOnlyNo
nameFilterNo
topNo

Implementation Reference

  • Implementation of the dynamics_list_solutions tool handler.
    server.tool(
      "dynamics_list_solutions",
      "Lista soluções instaladas no Dynamics CRM",
      ListSolutionsSchema.shape,
      async (params: z.infer<typeof ListSolutionsSchema>) => {
        const filters: string[] = ["isvisible eq true"];
        if (params.managedOnly) filters.push("ismanaged eq true");
        if (params.unmanagedOnly) filters.push("ismanaged eq false");
        if (params.nameFilter) filters.push(`contains(friendlyname,'${params.nameFilter}')`);
    
        const result = await client.list("solutions", {
          select: ["solutionid", "uniquename", "friendlyname", "version", "ismanaged", "description", "createdon", "modifiedon", "installedon"],
          filter: filters.join(" and "),
          orderby: "friendlyname asc",
          top: params.top,
          expand: "publisherid($select=friendlyname,customizationprefix)",
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Soluções encontradas: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
    
    // 3. Add Component to Solution
  • Schema definition for dynamics_list_solutions inputs.
    export const ListSolutionsSchema = z.object({
      managedOnly: z.boolean().default(false),
      unmanagedOnly: z.boolean().default(false),
      nameFilter: z.string().optional(),
      top: z.number().default(50),
    });
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. The description only states it lists installed solutions but doesn't mention important behavioral aspects like whether this is a read-only operation, what permissions are required, how results are returned (pagination, format), or any rate limits. For a list operation with zero annotation coverage, this is insufficient.

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 extremely concise - a single sentence in Portuguese that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. It's front-loaded with the essential information in minimal words.

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 that this is a list operation with 4 parameters (0% schema coverage), no annotations, and no output schema, the description is incomplete. It doesn't explain what parameters do, what the return format looks like, or any behavioral constraints. For a tool with this complexity and lack of structured documentation, the description should provide more context about how to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 4 parameters have descriptions in the schema. The tool description provides no information about any parameters - it doesn't mention filtering options, pagination controls, or any of the actual parameters (managedOnly, unmanagedOnly, nameFilter, top). The description fails to compensate for the complete lack of parameter documentation in the schema.

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 verb ('Lista' - Portuguese for 'List') and resource ('soluções instaladas no Dynamics CRM'), making the purpose understandable. However, it doesn't differentiate this tool from other list tools in the sibling set (like dynamics_list_columns, dynamics_list_tables, etc.), which would require a 5.

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. The description doesn't mention prerequisites, context, or how this differs from other list operations in the Dynamics CRM toolset. It simply states what the tool does without usage 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