Skip to main content
Glama

find_unused_objects

Scan a Power BI semantic model and report layout to identify unused measures and unreferenced columns for model cleanup.

Instructions

Scan the semantic model and report layout to identify unused measures and unreferenced columns.

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

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
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 behavioral burden. "Scan ... and report" implies a read-only operation and usefully discloses that it inspects two artifacts (model plus report layout), but it never defines what counts as "unused" or "unreferenced" (e.g., unreferenced by visuals vs. by other measures), nor does it mention cost or scope of the scan.

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 well-formed sentence with the action and the two result categories front-loaded; nothing is wasted. It could have used a second short clause to clarify scope, but there is no filler.

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?

With an output schema present, return values need no explanation, and the single optional parameter is fully documented in the schema. The only meaningful gap is the undefined notion of "unused," which an agent may need in order to interpret results correctly.

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 coverage is 100% with a single optional workspace parameter whose description already explains the server-bound fallback. The tool description adds no scoping semantics beyond the schema, so the baseline of 3 applies.

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+resource ("Scan the semantic model and report layout") and names concrete outputs (unused measures, unreferenced columns). It is functionally distinguishable from siblings like analyze_impact or check_model_bpa, though it never names an alternative outright.

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 explicit when-to-use, when-not-to-use, or alternative routing; the agent must infer that this is for cleanup/audit scenarios. Nothing tells the caller how this differs from check_model_bpa or analyze_impact when deciding among analysis tools.

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