Skip to main content
Glama
Sign In
WizTree MCP

WizTree MCP

by onmokoworks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Top Entries

top_entries

Extract the largest files, folders, or all rows from a WizTree CSV snapshot, sorted by size or allocated space.

Instructions

List the largest files, folders, or all rows from a WizTree CSV snapshot.

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": {
      "csvPath": "<csvPath>"
    },
    "name": "top_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvPathYes
kindNoall
byNosize
limitNo

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?

No annotations exist, and the description only mentions listing, without disclosing read-only nature, error handling, or performance implications, which reduces transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but under-specified; it lacks detail on parameters and output, making it minimally acceptable for conciseness.

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?

With no output schema and limited description, the return format is unknown. The tool's behavior for kind=all (potentially large output) is not addressed, making it incomplete for effective use.

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

Parameters1/5

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

Schema descriptions are absent (0% coverage), and the tool description does not explain any parameters (csvPath, kind, by, limit), leaving agents without necessary context for correct invocation.

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 clearly states the tool lists largest files, folders, or all rows from a WizTree CSV snapshot, distinguishing it from sibling tools like analyze_csv or compare_csv.

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 purpose implies usage for viewing top entries, but no explicit guidance on when not to use it or alternatives is provided, leaving some ambiguity.

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