Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_get_web_resource_content

Retrieve and decode Base64 web resource content from Microsoft Dynamics CRM for development workflows and system management.

Instructions

Recupera o conteúdo de um web resource (decodificado de Base64)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webResourceIdYesID do web resource

Implementation Reference

  • The implementation of the `dynamics_get_web_resource_content` tool handler, which retrieves and decodes a web resource's content from the Dataverse CRM.
    server.tool(
      "dynamics_get_web_resource_content",
      "Recupera o conteúdo de um web resource (decodificado de Base64)",
      z.object({ webResourceId: z.string().describe("ID do web resource") }).shape,
      async (params: { webResourceId: string }) => {
        const result = await client.get<Record<string, unknown>>(
          `webresourceset(${params.webResourceId})?$select=name,displayname,content,webresourcetype,description`
        );
    
        let decodedContent = "";
        if (result.content) {
          decodedContent = Buffer.from(result.content as string, "base64").toString("utf-8");
        }
    
        return {
          content: [
            {
              type: "text" as const,
              text: `**${result.name}** (${result.displayname})\n\nConteúdo:\n\`\`\`\n${decodedContent}\n\`\`\``,
            },
          ],
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions Base64 decoding, which is useful behavioral context. However, it lacks details on permissions required, rate limits, error handling (e.g., for invalid IDs), or what the output looks like (e.g., raw content format).

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 no wasted words. It's appropriately sized for a simple retrieval operation and front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally adequate. It covers the core action and Base64 decoding, but lacks context on usage, permissions, or output format, which would be helpful for an AI agent to invoke it correctly.

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%, with the parameter 'webResourceId' clearly documented in the schema. The description doesn't add any additional meaning about the parameter beyond what the schema provides, such as format examples or where to obtain the ID. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('recupera' meaning retrieves) and resource ('conteúdo de um web resource'), specifying it's decoded from Base64. It distinguishes from siblings like 'dynamics_list_web_resources' (which lists resources) and 'dynamics_create_web_resource' (which creates them), but doesn't explicitly mention this distinction in the description itself.

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. It doesn't mention prerequisites (e.g., needing an existing web resource ID), when not to use it, or refer to sibling tools like 'dynamics_list_web_resources' for obtaining IDs first.

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