Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Disk Usage Report

disk_usage_report
Read-only

Rank immediate subfolders by disk usage under a given path to locate disk hogs and see where storage is consumed.

Instructions

Report the largest immediate subfolders under a given path to help find disk hogs.

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": {
      "path": "<path>"
    },
    "name": "disk_usage_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
top_nNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely useful behavior: it is non-recursive (only 'immediate' subfolders) and ranked by size, which is not derivable from the schema. It omits how errors (missing path, permission denied) are surfaced and whether sizes are cached or computed.

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?

A single sentence with zero filler, front-loading the operation and its purpose. Nothing to cut or reorder.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and the read-only annotation covers safety. However, with 0% schema coverage the description leaves top_n completely undocumented and gives no hint on ranking/tie behavior, which is a real gap for a two-parameter analytic tool.

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?

Schema description coverage is 0%, so the description must carry the parameter burden. 'Under a given path' adds meaning to path, but top_n is never mentioned, so the agent has no description-level hint about limiting result count or what the default of 10 implies.

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?

Specific verb (report) and resource (largest immediate subfolders under a path), plus a stated goal (find disk hogs). It implicitly distinguishes itself from list_directory by ranking by size and stopping at the immediate level, though no sibling is named explicitly.

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?

'To help find disk hogs' implies a diagnostic use case, but there is no explicit when-to-use versus list_directory (the obvious alternative for path browsing) and no when-not-to-use or prerequisite guidance.

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