Skip to main content
Glama
Sign In
pbi-doc-generator

pbi-doc-generator

by djrien-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pbi_list_models

List documented Power BI semantic models with workspace, refresh status, source connectors, table/measure counts, and health warnings; filter by model, source type, or workspace.

Instructions

List documented Power BI semantic models with workspace, refresh status, source connectors, table/measure counts, and health warnings.

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": "pbi_list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional substring filter on model name or source type.
workspaceNoOptional case-insensitive workspace name filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose the returned fields and implies a read-only enumeration, which is useful. However, it says nothing about result limits, pagination, permissions, or what a 'health warning' or 'documented' means in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 attribute list follows. The trailing enumeration is dense but each item is informative, so little is wasted.

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?

With no output schema and no annotations, the description does well to enumerate the returned attributes, which is the main missing piece elsewhere. It still lacks operational details (result caps, whether listings are truncated, read-only confirmation) and any routing guidance among the seven sibling tools.

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 both parameters are optional with documented semantics, so the schema does the heavy lifting and a 3 is the baseline. The description adds no extra meaning for the search or workspace filters, and its mention of 'workspace' as a returned field is not distinguished from the workspace filter 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 gives a specific verb and resource ('List documented Power BI semantic models') and enumerates the attributes surfaced (workspace, refresh status, connectors, counts, health warnings), so the agent knows exactly what the tool returns. It does not name or contrast any sibling such as pbi_inspect_model or pbi_catalog_summary, so differentiation is left implicit.

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, when-not-to-use, or alternative guidance; the agent must infer that this is a catalog-browsing tool from the word 'List'. The qualifier 'documented' hints at scope but is never explained, and nothing indicates whether to prefer this over pbi_catalog_summary or pbi_inspect_model.

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

Deploy Server

Other Tools