Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_publishers

Retrieve available publishers from Microsoft Dynamics CRM to manage solution components and deployment workflows.

Instructions

Lista publicadores disponíveis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customOnlyNo

Implementation Reference

  • Handler implementation for the dynamics_list_publishers tool.
    server.tool(
      "dynamics_list_publishers",
      "Lista publicadores disponíveis",
      ListPublishersSchema.shape,
      async (params: z.infer<typeof ListPublishersSchema>) => {
        const filter = params.customOnly ? "iscustomizable/Value eq true" : undefined;
    
        const result = await client.list("publishers", {
          select: ["publisherid", "uniquename", "friendlyname", "customizationprefix", "customizationoptionvalueprefix", "description"],
          filter,
          orderby: "friendlyname asc",
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Publicadores encontrados: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
  • Schema definition for the dynamics_list_publishers tool inputs.
    export const ListPublishersSchema = z.object({
      customOnly: z.boolean().default(true),
    });
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. It only states it lists publishers without disclosing behavioral traits like whether it's read-only, requires authentication, has rate limits, returns paginated results, or what format the output takes. This is inadequate for a tool with zero annotation coverage.

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 with zero wasted words. It's appropriately sized for a simple listing tool and front-loaded with the core action, though it could benefit from more detail.

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 simple input schema with one parameter, the description is incomplete. It doesn't explain what 'publishers' are, how results are returned, or any behavioral context, making it insufficient for an agent to use the tool effectively without additional inference.

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

Parameters4/5

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

With only one parameter and 0% schema description coverage, the description doesn't mention the parameter at all. However, since there's only one parameter and it's optional with a default value, the baseline is high. The description doesn't add meaning beyond the schema, but the minimal parameter count keeps the score from being lower.

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 publicadores disponíveis' (List available publishers) states a clear verb ('Lista') and resource ('publicadores'), but it's vague about scope and doesn't differentiate from siblings like 'dynamics_list_solutions' or 'dynamics_list_tables'. It lacks specificity about what 'publishers' are in this 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. With many sibling tools for listing different resources (e.g., solutions, tables, columns), the description offers no context about prerequisites, typical use cases, or exclusions, leaving the agent to guess based on the name alone.

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