Skip to main content
Glama
x746b

mac_forensics-mcp

by x746b

mac_spotlight_search

Search macOS Spotlight index to retrieve file metadata, including data from deleted files. Filter by filename, path, content type, inode, or time range.

Instructions

Search Spotlight index for file metadata. Contains info even for deleted files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inodeNoFind file by inode number
limitNo
offsetNo
filenameNoFilter by filename (substring)
time_endNoISO datetime - filter before this time
time_startNoISO datetime - filter after this time
content_typeNoFilter by content type (e.g., 'public.executable')
path_containsNoFilter by path substring
spotlight_pathYesPath to .store.db or .Spotlight-V100 directory
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions that deleted files are included, but does not disclose read-only nature, permission requirements, or potential side effects. This is insufficient for a search tool.

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?

Two sentences with no wasted words. The action is front-loaded. Ideal length for a simple search tool.

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?

Despite 9 parameters and no output schema, the description omits crucial context like return format, ordering, or pagination behavior. The note about deleted files is helpful but insufficient for comprehensive understanding.

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 high (78%), and the description adds no further parameter details. The baseline of 3 is appropriate as the schema already documents parameters adequately.

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 searches the Spotlight index for file metadata and highlights that it includes deleted files, which is a key differentiator. It is distinct from sibling tools like mac_spotlight_stats.

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. There is no mention of prerequisites, limitations, or complementary tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x746b/mac_forensics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server