Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_columns

Retrieve column attributes from Dynamics CRM tables to understand data structure and customize entity fields for development workflows.

Instructions

Lista colunas (atributos) de uma tabela

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityLogicalNameYesNome lógico da entidade
customOnlyNo

Implementation Reference

  • The handler implementation for the "dynamics_list_columns" tool, which queries the Dataverse API to fetch column metadata for a specified entity.
    // 4. List Columns
    server.tool(
      "dynamics_list_columns",
      "Lista colunas (atributos) de uma tabela",
      ListColumnsSchema.shape,
      async (params: z.infer<typeof ListColumnsSchema>) => {
        let filter = "";
        if (params.customOnly) {
          filter = "&$filter=IsCustomAttribute eq true";
        }
    
        const result = await client.get<{ value: Record<string, unknown>[] }>(
          `EntityDefinitions(LogicalName='${params.entityLogicalName}')/Attributes?$select=LogicalName,SchemaName,DisplayName,AttributeType,RequiredLevel,Description,IsCustomAttribute${filter}`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Colunas de ${params.entityLogicalName}: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
  • The input schema definition for the "dynamics_list_columns" tool, defining the required entity name and optional custom filter.
    export const ListColumnsSchema = z.object({
      entityLogicalName: z.string().describe("Nome lógico da entidade"),
      customOnly: z.boolean().default(false),
    });
  • The registration of the "dynamics_list_columns" tool within the server tool registry.
    server.tool(
      "dynamics_list_columns",
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. It states the tool lists columns but doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, or what happens when the entity doesn't exist. For a read operation 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 that directly states the tool's purpose. There's no wasted language or unnecessary elaboration - every word contributes to understanding what the tool does.

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 tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral constraints. While concise, it lacks necessary context for effective tool invocation in a complex Dynamics environment.

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 50% (only 'entityLogicalName' has a description). The description doesn't mention either parameter or provide any additional semantic context about what 'customOnly' means or how entity names should be formatted. It doesn't compensate for the schema's gaps, so baseline 3 is appropriate.

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 ('Lista' - list) and resource ('colunas de uma tabela' - columns of a table). It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'dynamics_get_forms' or 'dynamics_get_views' which also retrieve metadata.

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 about when to use this tool versus alternatives. While the sibling list includes many metadata retrieval tools (like 'dynamics_list_tables', 'dynamics_list_solutions'), the description offers no comparison or context for choosing this specific column-listing tool.

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