Skip to main content
Glama

search_measures

Find measures across a Power BI semantic model by name, DAX expression, or description, returning each measure's table, name, DAX, and description; filter by table or workspace.

Instructions

Find measures across the semantic model and return their table, name, DAX expression, and description.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive search term matching measure name, DAX, or description.
tableNoOptional table name filter.
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 burden. It does implicitly establish read-only behavior by promising returned records and names the returned fields, which is useful. However, it is silent on important behavioral details: whether omitting the query returns all measures, default workspace resolution, result-size or pagination limits, and whether the search is scoped to one model or many.

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, well-formed sentence with the action and scope front-loaded and the output fields listed compactly. There is no filler or redundancy.

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 an output schema present, the description need not explain return values, and its listing of returned fields is a bonus. But for a three-optional-parameter search tool with no annotations, it leaves real gaps: the meaning of an empty query, workspace scoping, and result limits are all unaddressed.

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%, so all three parameters (query, table, workspace) are already documented with defaults and matching semantics, which sets the baseline at 3. The description adds no parameter-level meaning beyond the schema; it only mentions the return shape.

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?

States a specific verb ("Find") and resource ("measures") plus the scope ("across the semantic model") and the four fields returned (table, name, DAX expression, description). An agent immediately knows this is a search/read operation. It stops short of differentiating from siblings such as find_unused_objects or generate_measure_docs, which also operate on measures.

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?

The description gives no when-to-use or when-not-to-use guidance and never names an alternative, even though the sibling set contains several measure-related tools. The only implied usage is "searching for measures", which the agent must infer from the name alone.

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