mcp_get_tables

Summary

Field	Value
Tool name	get_tables
MCP title	Inspect table metadata, columns, and relationships
Category	basic
Implementation	DynamicsCrm.DevKit.Cli/Mcp/Tools/GetTablesTool.cs
Estimated token count	~266 tokens (tools/list tool JSON, o200k_base, measured 2026-06-18)
Last verified	2026-06-18

MCP Tool Description (Exact)

Dataverse entity metadata. entity_name empty = list (filter by keyword/custom_only/names; includes IsAuditEnabled). Set = detail (attributes, relationships, alternate keys).

WHEN TO USE:
- Discover entity/attribute names before building FetchXML
- Find join columns, picklist options, required fields, primary key
- Audit settings on a set of entities (use names= with solution entity list)

MODE/CONVENTION:
- names= filters by exact logical-name list; filter= uses contains (list) or prefix (detail).

Parameters

Name	Type	Required	Default	Description
entity_name	string	No	""	Logical name → detail mode. Empty = list mode.
filter	string	No	""	LIST: keyword filter on entity. DETAIL: prefix filter on attributes/relationships.
custom_only	boolean	No	false	LIST: only custom entities.
include_intersect	boolean	No	false	LIST: include N:N intersect entities.
names	string	No	""	LIST: comma-separated logical names. Overrides filter/custom_only.

Input Schema

{
  "type": "object",
  "properties": {
    "entity_name": {
      "type": "string",
      "description": "Logical name → detail mode. Empty = list mode.",
      "default": ""
    },
    "filter": {
      "type": "string",
      "description": "LIST: keyword filter on entity. DETAIL: prefix filter on attributes/relationships.",
      "default": ""
    },
    "custom_only": {
      "type": "boolean",
      "description": "LIST: only custom entities.",
      "default": false
    },
    "include_intersect": {
      "type": "boolean",
      "description": "LIST: include N:N intersect entities.",
      "default": false
    },
    "names": {
      "type": "string",
      "description": "LIST: comma-separated logical names. Overrides filter/custom_only.",
      "default": ""
    }
  },
  "required": []
}

Related MCP Resources

This tool does not require any MCP resources.

When To Use

• Discover entity/attribute names before building FetchXML
• Find join columns, picklist options, required fields, primary key
• Audit settings on a set of entities (use names= with solution entity list)

Notes

• Use the exact MCP description and parameter schema above as the authoritative contract.

Example

{
  "entity_name": "string"
}

Output

Returns Task<CallToolResult> from the MCP server. The response content and structured fields follow the tool implementation and model returned by GetTablesTool.get_tables.

Prompt Examples

• "Show metadata for the Account table, including attributes and relationships."
• "List custom tables that have auditing enabled."
• "Find the logical name and option values for fields containing Status."