Skip to main content
Glama
Sign In
adversarial-rea

adversarial-rea

by Cultistsid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

analyze_binary

Extracts binary metadata, symbols, strings, and security signals from a target path to support evidence-first native binary triage.

Instructions

Extract binary metadata, symbols, strings, and security info from a target

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

Input Schema

NameRequiredDescriptionDefault
target_pathYesPath to target binary
strings_min_lenNoMinimum string length

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only extraction but does not state whether analysis executes the binary, what permissions are required, how long it takes, or what the output looks like. The categories of extracted info are mentioned, but this is insufficient for a multi-function analyzer with no structured safety metadata.

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 a single front-loaded sentence with no filler. It is appropriately sized for an overview, though it could have included a short qualifying clause about scope relative to sibling tools.

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

Completeness2/5

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

With no annotations, no output schema, and many sibling tools that overlap in surface area, the description is too sparse. It does not clarify output granularity, whether files are statically inspected or executed, or how the combined 'security info' relates to check_security.

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%, and both target_path and strings_min_len are documented in the schema. The description adds no parameter-level details beyond what the schema already provides, so the baseline 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 gives a specific verb (extract) and resource (binary metadata, symbols, strings, security info), so the purpose is clear. However, it does not distinguish this tool from siblings like get_symbols, get_strings, check_security, or get_headers, leaving ambiguity about whether this is an aggregate shortcut or a separate capability.

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?

There is no guidance on when to use this tool versus the many overlapping siblings such as get_symbols, get_strings, or check_security. No exclusions, prerequisites, or alternative-selection criteria are stated, so an agent must infer usage from the name alone.

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