Skip to main content
Glama
Sign In
mac-doctor-mcp

mac-doctor-mcp

by Krezzy88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_large_files

Scan an allowed directory to find files above a size threshold without modifying them, returning up to a set limit.

Instructions

Finds large files in an allowed directory without modifying them.

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": {
      "directoryPath": "<directoryPath>",
      "minSizeMB": "<minSizeMB>",
      "limit": "<limit>"
    },
    "name": "find_large_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMaximum number of matching files to return.
minSizeMBYesMinimum file size in MiB.
directoryPathYesDirectory to scan; must be inside Downloads, Documents, Projects, or an allowed cache directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It does helpfully assert that files are not modified (a read-only signal) and that scanning is restricted to allowed directories, but it says nothing about recursion depth, ordering of results, permission errors, or whether hidden files are included — significant gaps for a filesystem scan.

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?

A single tight sentence with no filler, and the read-only guarantee is front-loaded. It is efficient, though it is arguably under-specified rather than concise, leaving no room for routing or scoping detail.

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?

For a three-required-parameter filesystem scan with no annotations and no output schema, the description should at least indicate what a result contains (path, size, count) or how ordering works. The schema covers inputs fully, but the return behavior and the read-only boundary are left largely unexplained.

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?

Schema description coverage is 100%, so the input schema already defines directoryPath, minSizeMB, and limit including units and the allowed root list. The description adds only the general 'allowed directory' notion, which the schema states more precisely, so no meaning is added beyond the structured data; baseline 3 applies.

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 states a concrete verb and resource ('finds large files') plus the scope ('in an allowed directory'), which is specific enough for an agent to identify the operation. It does not name or contrast with the siblings analyze_caches and diagnose_disk_pressure, so the differentiation is only implicit.

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?

There is no guidance on when to choose this tool over analyze_caches or diagnose_disk_pressure, no prerequisites, and no exclusions beyond the passing mention of an 'allowed directory'. The agent must infer the use case (spotting oversized files to reclaim space) entirely on its own.

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