Skip to main content
Glama
rafteles2016

MCP Dynamics CRM Server

by rafteles2016

dynamics_list_tables

Retrieve and filter Dynamics CRM entity tables to identify custom or specific data structures for development and integration workflows.

Instructions

Lista tabelas (entidades) do Dynamics CRM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFiltro OData
customOnlyNoApenas tabelas customizadas
topNo

Implementation Reference

  • The implementation of the `dynamics_list_tables` tool, including the definition, schema validation, and handler logic.
    server.tool(
      "dynamics_list_tables",
      "Lista tabelas (entidades) do Dynamics CRM",
      ListTablesSchema.shape,
      async (params: z.infer<typeof ListTablesSchema>) => {
        const filters: string[] = [];
        if (params.customOnly) {
          filters.push("IsCustomEntity eq true");
        }
        if (params.filter) {
          filters.push(params.filter);
        }
    
        const result = await client.get<{ value: Record<string, unknown>[] }>(
          `EntityDefinitions?$select=LogicalName,SchemaName,DisplayName,EntitySetName,Description,IsCustomEntity,OwnershipType,PrimaryIdAttribute,PrimaryNameAttribute&$filter=${filters.join(" and ")}&$top=${params.top}`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Tabelas encontradas: ${result.value.length}\n\n${JSON.stringify(result.value, null, 2)}`,
            },
          ],
        };
      }
    );
  • The Zod schema definition for input validation for the `dynamics_list_tables` tool.
    export const ListTablesSchema = z.object({
      filter: z.string().optional().describe("Filtro OData"),
      customOnly: z.boolean().default(true).describe("Apenas tabelas customizadas"),
      top: z.number().default(50),
    });
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 states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits like pagination (implied by 'top' parameter), rate limits, authentication needs, or what the output looks like. This leaves significant gaps for agent understanding.

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. It's appropriately sized and front-loaded with no wasted words, making it easy for an agent to parse quickly.

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 no annotations, no output schema, and 3 parameters (one without schema description), the description is incomplete. It doesn't explain return values, behavioral constraints, or usage context, leaving the agent with insufficient information to properly invoke this tool in the broader Dynamics CRM ecosystem.

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 67% (2 of 3 parameters have descriptions). The description adds no parameter semantics beyond what's in the schema. With moderate schema coverage, the baseline score of 3 is appropriate since the schema does most of the work, but the description doesn't compensate for the undocumented 'top' parameter.

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 verb ('Lista' - List) and resource ('tabelas (entidades) do Dynamics CRM'), making the purpose evident. However, it doesn't explicitly differentiate this tool from other list tools in the sibling set like 'dynamics_list_columns' or 'dynamics_list_solutions', which would be needed for a score of 5.

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. With many sibling tools available, including other list operations, there's no indication of context, prerequisites, or exclusions that would help an agent choose appropriately.

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