Skip to main content
Glama

search

Search hex patterns, values, and functions across binary, PE, APK, and file formats to locate offsets, code, and field data for game-modding inspection and patching.

Instructions

Search in files. Dispatches by module+action.

Modules/actions: hex: hex_search (path, query, mode, offset, limit), diff_files (path_a, path_b), value_scan (before_path, after_path, value_type) pe: find_function (path, name|string_ref) apk: smali_search (src_dir, query, limit) format: guess_fields (path, max_fields)

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": {
      "module": "<module>",
      "action": "<action>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
moduleYes
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether these operations are read-only, whether value_scan/diff_files touch or snapshot files, expected runtime or limits, or how dispatch errors surface. Only the dispatch mechanics are described; the operational and safety profile is absent.

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 one-line purpose is front-loaded and the compact indented module/action table is dense with information and free of filler. Some of the shorthand is ambiguous ('name|string_ref', bare parameter lists with no delimiter between required and optional), which slightly undercuts machine parsing.

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?

With an output schema present, return values need not be explained, and the dispatch table covers the most critical unknown. What remains missing is material for a no-annotation tool: read-only guarantees, per-action required parameters, and failure behavior for invalid module/action combinations. For a multi-mode dispatcher this is adequate but not complete.

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

Parameters4/5

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

Schema coverage is 0% and 'params' is an opaque bag with additionalProperties, so the schema alone tells the agent nothing. The description compensates meaningfully by mapping each module+action to its expected parameter names (path, query, mode, offset, limit; path_a, path_b; before_path, after_path, value_type), which is the only source of that information. It stops short of types, defaults, or required-vs-optional per action, so it is not a 5.

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 names the verb and resource ('Search in files') and then enumerates the module:action dispatch surface (hex_search, diff_files, value_scan, find_function, smali_search, guess_fields), so an agent can see this is a polymorphic search front-end. It is clear, though the top-level sentence alone is broad; the specificity comes from the dispatch table rather than the summary line.

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 module/action listing implicitly tells the agent which branch fits which artifact (hex for binary diff/value scanning, pe for function lookup, apk for smali, format for field guessing), which is useful routing. However, there is no explicit when-to-use versus the sibling tools (inspect, diagnose, validate) and no statement of when a module is inapplicable or what happens with an invalid module+action pair.

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