ahk-mcp

AHK_Library_Import

Read-onlyIdempotent

Generate #Include statements to import AutoHotkey libraries, resolve dependencies automatically, and support multiple import formats for proper code organization.

Instructions

Generate #Include statements for importing a library. Resolves dependencies and provides correct import order. Supports different #Include formats (angle-brackets, relative, absolute).

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Library name (without .ahk extension)
`include_dependencies`	No	Include all dependencies in import order
`format`	No	Format for #Include statements	angle-brackets

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Feb 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations indicate read-only and idempotent operations, which the description aligns with by not contradicting them. The description adds valuable context beyond annotations, such as dependency resolution, import order, and support for different #Include formats, enhancing behavioral understanding without redundancy.

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 concise and front-loaded, consisting of two efficient sentences that directly state the tool's function and key features without unnecessary elaboration, making it easy to understand quickly.

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 moderate complexity, rich annotations, and full schema coverage, the description is mostly complete. It lacks details on output format (no output schema provided), but otherwise covers purpose and behavior adequately for a read-only, idempotent tool.

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 parameters. The description adds minimal semantic value by mentioning dependency resolution and format support, which relate to parameters but do not provide additional details beyond the schema's descriptions.

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's purpose with specific verbs ('Generate #Include statements for importing a library') and resources ('library'), and distinguishes it from siblings like AHK_Library_Info or AHK_Library_List by focusing on import statement generation rather than information retrieval or listing.

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?

The description implies usage for importing libraries with dependency resolution and format support, but does not explicitly state when to use this tool versus alternatives like AHK_Library_Info or AHK_Library_Search, nor does it provide exclusions or prerequisites.

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