Skip to main content
Glama
x746b

Windows Forensics MCP Server

by x746b
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

apmx_search_params

Search APMX capture files for API calls by parameter value, returning matching calls with highlighted parameters.

Instructions

Search API calls by parameter value in an APMX capture. Finds all calls where a specific integer (e.g., PID, handle, size) or string appears as a parameter value. Returns matching calls with the matched parameters highlighted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of matching calls to return
valueYesInteger or string value to search for in parameters
file_pathYesPath to .apmx64 or .apmx86 capture file
process_indexNoWhich process to search (0 = first/only process)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided; description fails to disclose performance characteristics, limitations, or error handling 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 concise sentences without waste; directly states purpose and output format.

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?

Adequate for a search tool; covers input and output basics but lacks details on return structure or edge cases.

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 coverage is 100% with descriptions; description adds minor context about searching integer or string values and highlighting matches.

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?

Clear verb 'Search' with resource 'API calls by parameter value' and distinct from siblings like apmx_get_calls.

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?

Implied usage from purpose, but no explicit when-to-use or alternatives; could benefit from context like 'use instead of apmx_get_calls when filtering by parameter value'.

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