Skip to main content
Glama

AHK_File_List

Read-only

List AutoHotkey files with search filters, wildcards, and pagination to manage AHK scripts efficiently.

Instructions

List AHK files with optional name search. Use nameFilter with wildcards (e.g., "Hotstring") to find specific files.

šŸ“Ž Active File: Not set. Use AHK_File_Active to select a target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryNoDirectory root to enumerate (defaults to active file directory or current working directory).
nameFilterNoFilter by filename pattern with * wildcards (e.g., "*Hotstring*", "GUI_*"). 1-200 characters.
recursiveNoInclude files from subdirectories.
includeDirectoriesNoInclude directories in the results.
includeHiddenNoInclude entries beginning with .
extensionsNoLimit results to specific file extensions (defaults to [".ahk"]). Use empty array to include all files.
offsetNoNumber of items to skip for pagination.
limitNoMaximum items to return per page.
maxDepthNoMaximum depth when recursive is true.
includeStatsNoInclude size/modified metadata.
absolutePathsNoReturn absolute paths in results.
outputFormatNoOutput format: compact (paths only ~minimal tokens), detailed (with stats), json (full data).compact
Behavior3/5

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

The annotation readOnlyHint=true already indicates this is a safe read operation. The description adds useful context about wildcard usage and references the active file state, but doesn't disclose additional behavioral traits like pagination behavior (implied by offset/limit parameters), rate limits, or error handling. It doesn't contradict the annotation.

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?

The description is extremely concise and well-structured: two sentences that efficiently convey the core functionality and a key usage note. Every word earns its place, with no redundant information or fluff.

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

Completeness4/5

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

Given the tool's complexity (12 parameters) and lack of output schema, the description is reasonably complete. It covers the main purpose and key usage aspects, though it could benefit from mentioning the extensive filtering options available via parameters. The annotations provide safety context, and the schema handles parameter documentation.

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?

With 100% schema description coverage, the input schema fully documents all 12 parameters. The description adds minimal value by mentioning nameFilter with wildcard examples, but doesn't provide additional semantic context beyond what's in the schema. This meets the baseline for high schema coverage.

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's purpose: 'List AHK files with optional name search.' It specifies the resource (AHK files) and verb (list) with an optional filtering capability. However, it doesn't explicitly differentiate from sibling tools like AHK_File_Recent or AHK_File_View, which might also list files in different contexts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for usage: it mentions using nameFilter with wildcards for specific searches and references AHK_File_Active for setting a target file. This gives practical guidance on when and how to use the tool, though it doesn't explicitly state when not to use it or compare it to alternatives like AHK_File_Recent.

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/TrueCrimeDev/ahk-mcp'

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