Skip to main content
Glama
sdebruyn

fabric-dw-mcp-cli

by sdebruyn
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

clear_cache

Clear stale name-to-UUID mappings for workspaces or items. Choose scope to remove cached entries and get count of cleared buckets.

Instructions

Erase cached workspace and item name-to-UUID mappings.

Args: scope: Which portion of the cache to clear.

    - ``"workspaces"`` — clear only workspace name→UUID entries.
    - ``"items"`` — clear only item (warehouse/endpoint) entries.
    - ``"all"`` (default) — clear all entries.

Returns: A dict with keys scope (the value used), workspaces_cleared (number of workspace entries removed), and items_cleared (number of item workspace buckets removed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It explains the effect (erase cache), scope options, and return values. However, it does not disclose potential side effects, permission requirements, or whether the operation is reversible, which would improve transparency.

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?

The description is well-structured with concise 'Args' and 'Returns' sections, using bullet points for enum values. It is front-loaded with the main action and contains no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and an output schema mentioned, the description covers all necessary aspects: effect, parameter options, and return values. It is fully complete.

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

Parameters5/5

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

Despite schema description coverage being 0%, the description thoroughly explains the sole parameter 'scope' with enum values and default. This goes beyond the schema by providing clear semantics for each option.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Erase') and resource ('cached workspace and item name-to-UUID mappings'). It clearly distinguishes itself from sibling tools like 'clear_table' which operates on different data.

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?

No guidance on when to use this tool versus alternatives or when not to use it. The description only explains what it does, lacking explicit usage context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sdebruyn/fabric-dw-mcp-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server