Skip to main content
Glama

refresh_workspaces

Re-scan configured workspace roots to discover and update PBIP projects, keeping local Power BI authoring views current after file or folder changes.

Instructions

Re-scan configured workspace roots and refresh discovered PBIP projects.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full disclosure burden and mostly doesn't: it doesn't say whether this touches the filesystem, whether it mutates cached/discovered project state, whether it is expensive or slow on large roots, or what happens to previously discovered projects that no longer exist. "Refresh" strongly implies state change but the safety and cost profile remain unknown. The presence of an output schema covers return values but not the side-effect story.

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 sentence with no filler, front-loading the re-scan action and its target. Nothing is redundant or buried.

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 zero-parameter tool with an output schema, most of the calling mechanics are covered, but the absence of annotations plus silence on side effects, cost, and idempotency leaves a meaningful gap. An agent can invoke it but cannot predict what it changes or when it should be preferred over list_workspaces.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The phrase "configured workspace roots" usefully signals that scope is determined by external configuration rather than a call argument.

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 action pair — "re-scan configured workspace roots" and "refresh discovered PBIP projects" — which tells an agent this re-enumerates on-disk projects rather than listing existing ones like list_workspaces. It doesn't explicitly name how it differs from validate_workspace, but the verb and object are concrete enough to act on.

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 word "re-scan" implies the tool is for picking up projects added or changed on disk since the last scan, but that condition is never stated. There is no when-to-use vs. when-not guidance, no mention of whether a prior list_workspaces or validate_workspace call should precede it, and no stated prerequisites such as configured roots being required.

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