Skip to main content
Glama

validate_workspace

Run structural and syntax validation across TMDL and PBIR report JSON to catch errors before deploying or editing a Power BI workspace.

Instructions

Run structural and syntax validation across TMDL and PBIR report JSON.

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

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.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 disclosure burden. It reveals the validation scope (TMDL plus PBIR) but never states that the operation is read-only and non-destructive, how findings are reported, whether validation is workspace-wide or scoped, or whether it is expensive to run at scale.

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?

One sentence, front-loaded with the action and the artifacts covered, with no filler. Its brevity comes at the cost of necessary behavioral detail rather than verbosity, so the structure itself is clean.

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?

An output schema exists, so return values need not be described, and the single parameter is optional and well documented. However, the absence of annotations means the description should have compensated by stating the read-only nature and the relationship to sibling validation tools, which it does not.

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%: the single optional 'workspace' parameter is fully documented in the schema, including the fallback to a server-bound workspace. The description adds nothing about the parameter, but none is required given the schema completeness.

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?

'Run structural and syntax validation across TMDL and PBIR report JSON' gives a specific verb (validate) and names the artifact types checked (TMDL, PBIR JSON), so the agent knows exactly what is inspected. It stops short of distinguishing itself from validation-adjacent siblings such as check_model_bpa or analyze_impact.

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?

No explicit when-to-use or when-not-to-use statement is present; the agent must infer that this is a pre-deployment/consistency check on workspace artifacts. No alternative tool is named, leaving the choice between this and check_model_bpa to guesswork.

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