Skip to main content
Glama
Sign In
qlik-lineage-mcp

qlik-lineage-mcp

by EngIcaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ghost_files

Identify unused data files in a Qlik Cloud space by scanning for files no app consumes. Reduce storage costs.

Instructions

Return data files in a space that no app in the tenant consumes.

Args: space_name: Display name of the space to scan. Case-insensitive.

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": {
      "space_name": "<space_name>"
    },
    "name": "ghost_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should fully disclose behavioral traits. It does not mention read-only nature, side effects, permissions, or error handling (e.g., space not found).

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 extremely concise, uses a structured Args format, and front-loads the main purpose. Every sentence adds value without redundancy.

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

Completeness2/5

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

Given the tool's simplicity and lack of output schema, the description should explain return values (e.g., list of file names). Current description only states what it returns but not the format or examples, leaving gaps.

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?

The schema coverage is 0%, so the description must add value. It states that space_name is the display name and case-insensitive, which helps. However, it does not specify expected format or constraints beyond that.

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?

The description clearly states the action (return) and resource (data files) with a specific context (space with no app consumption). It implicitly distinguishes from sibling 'unused_columns', but could be more precise about 'data files'.

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 like 'unused_columns'. The description only explains what it does without providing 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.

Deploy Server

Other Tools