Skip to main content
Glama
Heretek-RE

re-binary-diff

by Heretek-RE

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_binary_diffA

Return server status + version. Always status: OKre-binary-diff has no external system dependencies.

unified_diffA

Compute a unified-style diff between path_a and path_b.

For small files (<= 8 MiB per side) the function runs difflib.unified_diff over the byte streams (decoded as latin-1). For large files it falls back to a per-chunk SHA-256 diff.

Args: path_a: first file (the "before" or "original") path_b: second file (the "after" or "patched")

Returns::

{
  "path_a": "...",
  "path_b": "...",
  "size_a": N,
  "size_b": N,
  "mode": "sha256_equal" | "inline_unified_diff" | "chunk_sha256_diff",
  "equal": bool,
  "diff_lines": ["...", ...],   (inline mode)
  "chunk_diff": [{...}, ...],   (chunk mode)
}

The function is read-only. The "patched" copy at path_b is not modified.

fingerprint_sectionsA

Return a per-chunk SHA-256 + offset + size fingerprint of path.

Useful for finding the structural delta between two versions of a binary without loading either into memory. Pair with unified_diff (chunk mode) for large files.

Args: path: file to fingerprint chunk_size: bytes per chunk (default 1 MiB) max_chunks: 0 = no cap; > 0 = return at most N chunks

Returns::

{
  "path": "...",
  "size": N,
  "chunk_size": N,
  "truncated": bool,
  "chunks": [
    {"index": 0, "offset": 0, "size": 1048576, "sha256": "..."},
    ...
  ],
}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: a health check, a single-file fingerprint, and a two-file diff. There is no ambiguity about which tool to use for a given task.

Naming Consistency3/5

Tool names use different patterns: 'check_binary_diff' (verb_noun), 'fingerprint_sections' (verb_noun), and 'unified_diff' (adjective_noun). The mixing of conventions reduces consistency.

Tool Count4/5

With 3 tools, the server is well-scoped for binary diffing tasks. It covers the essential operations without excess, though some might argue a tool to list chunks could be merged.

Completeness4/5

The tool set covers the core workflow: fingerprint a file, compare two files, and check server status. There are minor gaps (e.g., no explicit tool to fetch specific chunks), but the provided tools are sufficient for the domain.

Maintenance

ActivityStale
ResponsivenessSyncing