Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_update_form

Update the XML of a form in Microsoft Dynamics CRM to modify its structure and functionality.

Instructions

Atualiza o XML de um formulário

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYesID do formulário
formXmlYesXML do formulário atualizado

Implementation Reference

  • The handler for the dynamics_update_form tool which updates the formxml and publishes the change.
    async (params: z.infer<typeof UpdateFormSchema>) => {
      await client.update("systemforms", params.formId, {
        formxml: params.formXml,
      });
    
      // Publish the entity
      return {
        content: [
          {
  • Registration of the dynamics_update_form tool.
    server.tool(
      "dynamics_update_form",
      "Atualiza o XML de um formulário",
      UpdateFormSchema.shape,
  • Input schema definition for the dynamics_update_form tool.
    export const UpdateFormSchema = z.object({
      formId: z.string().describe("ID do formulário"),
      formXml: z.string().describe("XML do formulário atualizado"),
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Atualiza' (updates) implies a mutation operation, but the description doesn't disclose important behavioral traits like permission requirements, whether this is a destructive operation, what happens to existing form configurations, or what the response looks like. For a mutation tool 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 a single, efficient sentence in Portuguese that directly states the tool's purpose. There's zero wasted language or unnecessary elaboration. It's appropriately sized for what it communicates.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'updating form XML' entails operationally, what permissions are required, what validation occurs, or what the response contains. The context signals show this is a 2-parameter tool performing updates, which requires more behavioral disclosure than provided.

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 both parameters (formId, formXml) are documented in the schema. The description mentions 'XML de um formulário' which aligns with the formXml parameter, but adds no additional semantic context beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 'Atualiza o XML de um formulário' clearly states the action (update) and resource (form XML) in Portuguese. It's specific about what gets updated (XML of a form), but doesn't differentiate from sibling tools like dynamics_update_column or dynamics_update_web_resource, which also perform updates on different resources.

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. There are multiple update-related sibling tools (dynamics_update_column, dynamics_update_web_resource), but the description doesn't explain when this specific form XML update is appropriate versus other form-related operations like dynamics_get_forms.

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