Skip to main content
Glama

get_table

Retrieve full schema for a specified table, including columns, measures, relationships, and SQL source, for Power BI model inspection.

Instructions

Retrieve complete table schema including columns, measures, relationships, and SQL source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table_name": "<table_name>"
    },
    "name": "get_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace identifier returned by list_workspaces (prefer workspace_id or unique name). Optional when the server is bound to a single workspace.
table_nameYesTable name to inspect.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Retrieve' signals a read-only operation and the sentence names what content comes back, which is useful, but it says nothing about error behavior for a missing table, permission requirements, or whether the SQL source requires elevated scopes — all meaningful for a schema-introspection call.

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?

A single front-loaded sentence with zero filler; the verb, scope, and returned components all appear immediately. Nothing could be cut without losing information.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and both parameters are fully documented in the schema. The remaining gap is routing guidance relative to get_table_sql and list_tables, plus any workspace-scoping caveat beyond what the schema states.

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%, including the workspace default and the optional-when-single-workspace note, so the schema already does this work. The description adds no meaning about table_name expectations (qualified vs unqualified names, case sensitivity), leaving the baseline score 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?

States a specific verb plus resource ('Retrieve complete table schema') and enumerates the returned components (columns, measures, relationships, SQL source), which distinguishes it in spirit from the narrower get_table_sql and the listing-oriented list_tables. It stops short of naming the sibling it differs from, so differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies the usage context — inspect one table — but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_table_sql for a SQL-only need or to list_tables for enumeration. An agent can infer the right call, but must do the inference itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.