Skip to main content
Glama
Sign In
secureaudit-mcp

secureaudit-mcp

by rev2ret
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

safe_extract_strings

Extract printable ASCII strings from binary files to locate hardcoded secrets, URLs, or indicators.

Instructions

Safely extracts print-printable ASCII strings from local binary files (mimicking the Linux 'strings' utility) to look for indicators, secrets, or hardcoded URLs.

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": {
      "filePath": "<filePath>"
    },
    "name": "safe_extract_strings"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesAbsolute path to the binary file to extract strings from.
minLengthNoMinimum character length of strings to extract (default is 4).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Safely extracts' implying non-destructive behavior, but omits details about authentication, error handling, performance, or side effects (e.g., file permissions).

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

Conciseness5/5

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

The description is a single, well-structured sentence that conveys the action, scope, and purpose without unnecessary words. It is front-loaded and efficient.

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 adequately explains what the tool does and its analogue, but lacks details about return values (no output schema), error conditions, or limitations. For a simple extraction tool, this is minimally adequate but not complete.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema: it mentions 'print-printable ASCII strings' but does not clarify the character set or filtering specifics not already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool extracts print-printable ASCII strings from local binary files, mimicking the Linux 'strings' utility, and specifies the purpose (look for indicators, secrets, hardcoded URLs). This distinguishes it from sibling tools like audit_source_code or check_binary_protections.

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 provides no explicit guidance on when to use this tool versus alternatives (e.g., audit_source_code). It mentions mimicking Linux 'strings' but does not clarify when extracting strings is preferred over other binary analysis tasks.

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