Skip to main content
Glama

pbi_search_dax_and_m

Search across all DAX measures, calculated columns, model Power Query M partitions, Dataflow Gen1/Gen2 M queries, and Native SQL in the catalog.

Instructions

Search across all DAX measures, calculated columns, model Power Query M partitions, Dataflow Gen1/Gen2 M queries, and Native SQL in the catalog.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "pbi_search_dax_and_m"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword, table, view, column, or function name to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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. It discloses catalog-wide scope across five artifact families, but says nothing about what a match looks like, whether matching is substring/case-insensitive, result limits, or whether it is read-only. For a search tool with zero annotation coverage this is a meaningful gap.

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?

One sentence, front-loaded with the verb, with a scope enumeration in which every clause adds information the agent needs (which artifact types are reachable). No filler or redundant restatement of the name.

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?

For a one-parameter search tool with no output schema and no annotations, the description establishes scope but not the shape or granularity of results, which an agent needs to decide whether to call it or a lineage tool instead. Adequate to invoke, incomplete for judging output usefulness.

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 a single parameter with 100% schema description coverage, so the schema already explains that it accepts a keyword, table, view, column, or function name. The description adds no syntax, matching, or format detail beyond that, so baseline 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?

States a specific verb ("Search") and enumerates the exact artifact types covered: DAX measures, calculated columns, model Power Query M partitions, Dataflow Gen1/Gen2 M queries, and Native SQL. That enumeration implicitly separates it from lineage/impact siblings, but no sibling is named or explicitly excluded.

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 search semantics make the general use case obvious (keyword lookup across the catalog), but there is no explicit when-to-use, no condition distinguishing it from pbi_measure_lineage or pbi_source_impact, and no statement about when it should not be used. Guidance is implied rather than stated.

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