Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_get_import_job_status

Check the status of a Dynamics CRM solution import job to monitor deployment progress and verify completion.

Instructions

Verifica o status de uma importação de solução

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
importJobIdYesID do job de importação

Implementation Reference

  • The handler implementation for the dynamics_get_import_job_status tool, which fetches import job status from Dataverse.
    // 8. Get Import Job Status
    server.tool(
      "dynamics_get_import_job_status",
      "Verifica o status de uma importação de solução",
      z.object({ importJobId: z.string().describe("ID do job de importação") }).shape,
      async (params: { importJobId: string }) => {
        const result = await client.get<Record<string, unknown>>(
          `importjobs(${params.importJobId})?$select=importjobid,solutionname,progress,startedon,completedon,data`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Status da importação:\n${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      }
    );
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. It only states what the tool does (checks status) without describing traits like whether it's read-only (implied but not confirmed), what status values might be returned, error conditions, or performance characteristics. For a tool with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse.

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 tool's complexity (status checking of an import job), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what status information is returned, possible outcomes (e.g., success, failure, in-progress), or how to interpret results. For a tool with no structured output documentation, this leaves significant gaps.

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?

The description adds no parameter information beyond what's in the schema, which has 100% coverage. The schema already documents the single parameter 'importJobId' with a clear description. Since schema coverage is high, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to.

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 tool's purpose as 'Verifica o status de uma importação de solução' (Checks the status of a solution import), which specifies the verb ('verifica' - checks) and resource ('importação de solução' - solution import). It distinguishes from siblings like 'dynamics_import_solution' (which performs the import) and 'dynamics_get_system_jobs' (which might check other job types), but doesn't explicitly contrast with all sibling tools.

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 (e.g., that an import job must already exist via 'dynamics_import_solution'), exclusions, or specific contexts. Usage is implied from the purpose but not explicitly stated.

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