ahk-mcp

AHK_Library_Info

Read-onlyIdempotent

Retrieve detailed information about AutoHotkey libraries including metadata, documentation, functions, classes, and dependencies for development and debugging.

Instructions

Get detailed information about a specific AutoHotkey library. Returns metadata, documentation, classes, functions, and dependencies.

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_Info"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Library name (without .ahk extension)
`include_dependencies`	No	Include dependency resolution details

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Feb 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, repeatable read operation. The description adds value by specifying the return content (metadata, documentation, classes, functions, dependencies), which isn't covered by annotations. However, it doesn't disclose other behavioral traits like rate limits, error conditions, or performance characteristics.

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 a single, efficient sentence that front-loads the core purpose and specifies the return content. There's no wasted verbiage or redundancy, making it easy to parse 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 (retrieving library details), annotations cover safety (read-only, idempotent), and the schema fully documents parameters, the description is reasonably complete. It specifies the return content, which compensates for the lack of an output schema. However, it could be more comprehensive by mentioning error cases or usage context.

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 schema fully documents both parameters (name and include_dependencies). The description doesn't add any parameter-specific details beyond what's in the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 verb ('Get') and resource ('detailed information about a specific AutoHotkey library'), making the purpose explicit. It distinguishes from siblings like AHK_Library_List (which likely lists libraries) and AHK_Library_Search (which likely searches for libraries) by focusing on retrieving metadata for a specific library. However, it doesn't explicitly contrast with these siblings in the description text.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like AHK_Library_List or AHK_Library_Search, nor does it specify prerequisites or exclusions. Usage is implied by the purpose but not explicitly stated.

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