Skip to main content
Glama

imports_exports

Lists a binary's imports and exports, filtering symbol names with a regex in-process so only matching results reach the caller.

Instructions

List imports/exports of a binary, filtered with a regex (done in-process so only matches reach the caller).

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": {
      "path": "<path>"
    },
    "name": "imports_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoboth
pathYes
limitNo
filterNoRegex on symbol names, e.g. 'socket|ssl|crypt|exec'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: the regex is applied in-process so only matching symbols are returned, which bounds the result payload. However, it never states that the operation is read-only/non-mutating, that the result set can be truncated, or how symbols are ordered, leaving significant behavioral gaps for an unannotated tool.

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; the parenthetical is short and adds real information about where filtering occurs. Slightly more useful structure would have been to name the filter parameter explicitly, but nothing is wasted.

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?

The operation is simple and has no output schema to explain, so the description covers the core premise adequately. The main shortfall is that result truncation via limit and the return fields of each symbol are left undocumented.

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

Parameters2/5

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

Schema coverage is only 25%, so the description should compensate; it explains only the filter parameter (a regex over symbol names, applied server-side). The limit parameter and its default of 50 are never mentioned, so the caller has no warning that results may be truncated, and kind is only obliquely implied by "imports/exports".

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?

"List imports/exports of a binary" is a specific verb plus resource, and the filter clause clarifies the output shape. It is clear on its own, but it never contrasts itself with related siblings such as extract_strings or list_functions, so the agent must infer the boundary.

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?

Usage is implied (symbol-level inspection of a binary), but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can guess it is the right call for import/export symbol enumeration, but the description does not route it there.

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