Skip to main content
Glama
Sign In
WizTree MCP

WizTree MCP

by onmokoworks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Analyze CSV

analyze_csv

Summarize disk usage from a WizTree CSV export. Input a CSV file path and optional top limit to get a concise overview of the largest directories and files.

Instructions

Summarize an existing 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": "analyze_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvPathYesPath to a WizTree CSV export.
topLimitNo

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 are provided, so the description carries the full burden. It only says 'Summarize' without detailing what the summary contains, whether it modifies data, or any output characteristics. The lack of behavioral disclosure is a significant gap.

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

Conciseness4/5

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

The description is a single sentence that efficiently conveys the core purpose. However, it could be slightly expanded to include key details without becoming verbose.

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 presence of two parameters, no output schema, and sibling tools, the description is insufficient. It does not explain the output format, what 'summarize' means in practice, or how topLimit affects results. The agent would have to infer or test to use this tool correctly.

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

Parameters2/5

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

Although csvPath has a schema description, the description adds nothing beyond it. The topLimit parameter lacks any semantic explanation in both schema and description; its purpose and effect on output are unclear. With 50% schema description coverage, the description fails to compensate.

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 'Summarize an existing WizTree CSV snapshot' clearly states the verb (summarize) and resource (WizTree CSV snapshot). It implicitly distinguishes from siblings like 'top_entries' and 'extension_summary' by indicating it summarizes the entire snapshot rather than focusing on specific aspects.

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?

The description provides no guidance on when to use this tool versus alternatives like 'compare_csv' or 'scan_path'. It does not mention prerequisites, context, or when not to use it.

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