Skip to main content
Glama

check_model_bpa

Run Best Practice Analyzer rules against a semantic model to detect issues in keys, relationships, data types, and DAX. Use it to validate model quality and catch problems early.

Instructions

Run Best Practice Analyzer rules against the semantic model (keys, relationships, types, DAX).

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

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it never says the operation is read-only, that it does not mutate the model, how many rules run, or whether results are severity-ranked. The word "Run" plus "against the semantic model" hints at analysis but nothing confirms safety or side-effect profile for a tool with zero annotation coverage.

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 scope enumeration in parentheses is compact and informative. It is terse to the point of omitting usage and safety context, but nothing in it 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?

The tool is simple (one optional parameter) and an output schema exists, so return values need not be described. What is missing is behavioral framing: whether the check is read-only and what class of findings to expect, which matters because no annotations are present.

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?

There is one optional parameter and the schema description coverage is 100%, including the note that workspace is optional when the server is bound to a single workspace. The description adds nothing about the workspace parameter, which is acceptable given the schema already handles it fully.

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 uses a specific verb and resource ("Run Best Practice Analyzer rules against the semantic model") and the parenthetical enumerates the checked categories (keys, relationships, types, DAX), so the agent can distinguish this from siblings like find_unused_objects or analyze_impact. It stops just short of explicitly contrasting itself with those siblings.

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 parenthetical list of checked categories implicitly signals when the tool is useful (model hygiene review), but there is no explicit when-to-use, no prerequisites, and no named alternative for adjacent tasks such as impact analysis. Usage must be inferred from scope rather than stated.

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