Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_get_bulk_operations

Monitor bulk operations like deletions and imports in Dynamics CRM to track system activities and manage data processing tasks.

Instructions

Monitora operações em massa (bulk delete, imports, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo

Implementation Reference

  • The handler function for 'dynamics_get_bulk_operations' which queries Dynamics 365 for bulk delete operations and failures.
    server.tool(
      "dynamics_get_bulk_operations",
      "Monitora operações em massa (bulk delete, imports, etc.)",
      GetBulkOperationStatusSchema.shape,
      async (params: z.infer<typeof GetBulkOperationStatusSchema>) => {
        const result = await client.list("bulkdeletefailures", {
          select: ["bulkdeletefailureid", "errordescription", "orderedqueryindex", "createdon"],
          orderby: "createdon desc",
          top: params.top,
        });
    
        const bulkDeletes = await client.list("bulkdeleteoperations", {
          select: [
            "bulkdeleteoperationid", "name", "statuscode", "statecode",
            "createdon", "successcount", "failurecount",
          ],
          orderby: "createdon desc",
          top: params.top,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `## Operações em Massa\n\n**Bulk Delete Operations:**\n${JSON.stringify(bulkDeletes.value, null, 2)}\n\n**Falhas Recentes:**\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
  • Schema definition for the inputs of the 'dynamics_get_bulk_operations' tool.
    export const GetBulkOperationStatusSchema = z.object({
      top: z.number().default(10),
    });
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 mentions monitoring bulk operations but fails to disclose critical behavioral traits: whether this is a read-only operation, if it requires specific permissions, how results are returned (e.g., list format, pagination), or any rate limits. The description is too minimal for a tool that likely interacts with system data.

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 ('Monitora operações em massa (bulk delete, imports, etc.)'), which is appropriately concise. However, it could be more front-loaded with key details, and the use of 'etc.' adds slight vagueness, but overall it's well-structured without wasted 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 the complexity of monitoring bulk operations, no annotations, no output schema, and low parameter coverage, the description is incomplete. It lacks details on behavior, output format, error handling, and how it fits with sibling tools, making it insufficient for an agent to use effectively without additional context.

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?

The input schema has one parameter 'top' with 0% description coverage, and the tool description adds no information about parameters. It doesn't explain what 'top' means (e.g., number of results, limit), its purpose, or how it affects the monitoring. With low schema coverage and no compensation in the description, this is inadequate.

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 'Monitora operações em massa (bulk delete, imports, etc.)' states the tool monitors bulk operations, which is a clear purpose. However, it's vague about what 'monitor' entails (e.g., list, check status, track progress) and doesn't distinguish it from sibling tools like dynamics_get_system_jobs or dynamics_get_import_job_status, which might overlap in monitoring functions.

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. It doesn't mention prerequisites, timing, or compare it to sibling tools such as dynamics_get_system_jobs or dynamics_get_import_job_status, 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