Skip to main content
Glama

list_tables

List all tables in a Power BI semantic model with column and measure counts plus native SQL status, so you can inspect model structure and identify SQL-backed tables before editing.

Instructions

List all tables in the semantic model with column/measure counts and native SQL status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tables"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/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. It does communicate the shape of what comes back (counts plus native SQL status) and the read-only nature is strongly implied by "list", but it says nothing about scoping, permissions, or whether a null workspace means all workspaces or the bound one.

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 no filler: the verb and resource come first and the returned attributes are tacked on last. Nothing could be removed without losing information.

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?

The tool is simple (one optional parameter, output schema present, so return values need no prose), which lowers the bar. Still, for a listing tool it omits whether results are paginated, ordered, or scoped when workspace is omitted, leaving a correctness-relevant gap.

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%, and the single workspace parameter is already documented as a workspace_id or unique name from list_workspaces. The description adds only the phrase "in the semantic model", which does not clarify how the workspace argument scopes the listing, so this sits at the baseline.

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?

"List all tables in the semantic model" gives a specific verb and resource, and the trailing clause previews the payload (column/measure counts, native SQL status). It is clear on its own, but it never distinguishes itself from the sibling get_table, so an agent must infer that this is the bulk variant while get_table is the single-item variant.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent gets no signal about when to reach for list_tables versus get_table or get_table_sql, and no note on whether the optional workspace narrows the listing or how a server-bound workspace changes behavior.

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