Skip to main content
Glama

analyze_impact

Identify where a measure or column is referenced across TMDL formulas and report visuals to assess change impact before editing.

Instructions

Analyze where a measure or column is referenced across TMDL formulas and report visuals.

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": {
      "term": "<term>"
    },
    "name": "analyze_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesMeasure or column name whose usage across TMDL and visuals should be analyzed.
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

A3.6/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 discloses the two data sources searched (TMDL formulas and report visuals), which is useful behavioral context, but never states that the operation is read-only, whether results are paginated, or how matches are reported — though an output schema exists to cover return shape.

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 front-loaded sentence with no filler; the verb, target, and both search scopes appear immediately.

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?

For a two-parameter read tool with a full output schema and complete parameter documentation, the description covers what is analyzed and where. The only meaningful gap is the absence of any read-only or result-shape statement, which the output schema largely mitigates.

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 both parameters are already documented, including the workspace fallback behavior. The description's 'measure or column' phrasing matches the schema's term definition without adding format or matching-rule detail, 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 (analyze) and a precise resource (references to a measure or column) plus the two scopes searched: TMDL formulas and report visuals. An agent can tell it is a reference/impact lookup rather than a mutation, though it does not explicitly contrast itself with siblings like find_unused_objects.

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?

Usage is only implied by the phrase 'where a measure or column is referenced' — the natural use case is impact analysis before renaming or deleting. There is no explicit when-to-use, when-not-to-use, or named alternative such as find_unused_objects for the inverse question.

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