Skip to main content
Glama
Sign In
adversarial-rea

adversarial-rea

by Cultistsid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_symbols

Extract functions, imports, and exports from a binary, with optional filtering by symbol name, to support triage and manual review.

Instructions

Extract symbols (functions, imports, exports) from binary

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": "get_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoall
filterNoLiteral substring to filter symbol names
target_pathYesPath to target binary

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?

With no annotations provided, the description carries the full burden, yet says nothing about read-only safety, output format, size limits, or whether the target must be a supported binary format. The only behavioral hint is the implicit correspondence between the listed categories and the type enum.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity borders on under-specification rather than optimized density.

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?

For a 3-parameter tool with no annotations and no output schema, the definition should clarify return shape (names only? addresses? per-category grouping?), supported binary formats, and safety profile. None of that is present, leaving gaps the structured fields do not fill.

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 67%, so the schema already documents target_path and filter, and the type enum is self-describing. The parenthetical listing functions/imports/exports marginally reinforces the enum values, but adds no syntax, default, or filtering behavior detail beyond the schema.

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?

A specific verb (Extract) plus resource (symbols) with a parenthetical enumerating the categories (functions, imports, exports) and the source (binary). It does not, however, distinguish itself from sibling extraction tools such as get_strings, get_sections, or analyze_binary.

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 explicit guidance on when to use this versus analyze_binary, get_strings, or get_sections. Usage is only implied by the verb phrase; no prerequisites, exclusions, or alternative routing are stated.

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