Skip to main content
Glama
Sign In
WizTree MCP

WizTree MCP

by onmokoworks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare CSV

compare_csv

Compare two WizTree CSV snapshots to identify the largest changes in disk usage by path.

Instructions

Compare two WizTree CSV snapshots by path and report the largest changes.

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": {
      "beforeCsvPath": "<beforeCsvPath>",
      "afterCsvPath": "<afterCsvPath>"
    },
    "name": "compare_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeCsvPathYes
afterCsvPathYes
kindNoall
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It mentions comparison by path and reporting largest changes, but lacks details on what 'largest changes' means, case sensitivity, error handling, or performance implications. The absence of annotations amplifies the gap.

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

Conciseness2/5

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

The description is a single sentence, which is front-loaded but critically under-specified. It lacks necessary detail, making it insufficient for effective tool selection and invocation.

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

Completeness1/5

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

Given the tool has 4 parameters, no output schema, and no annotations, the description is far from complete. It does not explain the output format, parameter semantics, or usage context, making it inadequate for an agent to use correctly.

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 description coverage is 0%, so the description must explain the 4 parameters. It does not mention any parameter names, types, or defaults, leaving the agent to infer from the schema alone. The description adds zero value beyond the schema.

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 tool compares two WizTree CSV snapshots and reports the largest changes, which is specific and distinct from sibling tools like analyze_csv or extension_summary. However, it doesn't explicitly differentiate from siblings, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives like analyze_csv or top_entries. The description does not mention prerequisites, constraints, or typical scenarios.

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