Skip to main content
Glama
Sign In
fuzzmind-frida-mcp

fuzzmind-frida-mcp

by fuzzmind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

frida_kernel_scan

Scans kernel memory for specified hex patterns. Provide start address, size, and pattern to locate memory regions.

Instructions

Scan kernel memory for a hex pattern. Requires kernel access.

address: start address (hex string). size: number of bytes to scan. pattern: Frida hex pattern (e.g. '48 8b ?? c3').

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": {
      "address": "<address>",
      "size": "<size>",
      "pattern": "<pattern>"
    },
    "name": "frida_kernel_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
sizeYes
patternYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states the action and a prerequisite, omitting behavioral details such as side effects (e.g., read-only), permissions, or return value format. This leaves the agent uninformed about safety and expected behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the main action, followed by parameter details. It efficiently conveys key information without verbosity, though a more structured list could improve readability.

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

Completeness3/5

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

The description covers the action and parameter semantics adequately for a simple scanning tool. However, it lacks information about the return value (e.g., what does it output?) and does not differentiate from similar sibling tools like frida_memory_scan beyond the kernel qualifier.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description fully explains all three parameters: 'address' should be a hex string, 'size' is byte count, and 'pattern' gives a Frida hex pattern example. This adds essential meaning beyond the schema titles.

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 it scans kernel memory for a hex pattern, specifying the action and resource. The 'kernel' qualifier helps distinguish it from user-space memory scan tools like frida_memory_scan, but it does not explicitly differentiate from other kernel memory tools (e.g., frida_kernel_read).

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 mentions 'Requires kernel access' as a prerequisite but provides no guidance on when to use this tool versus alternatives (e.g., frida_memory_scan, frida_checksum_memory). No explicit when-not-to-use or alternative recommendations.

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