Skip to main content
Glama
white-box-synthesis

white-box-synthesis

by AhmedKishki

white-box-synthesis

An MCP server for constructing passages from approved human-authored fragments. The core preserves human wording lineage through recorded edits. Meaning and causality need separate review.

It uses the five operations from the white-box synthesis reference.

Core workflow

synthesise takes a passage plan, ordered arguments, approved fragments, and optional constraints. Without a candidate or gap, it returns needs_agent. The calling agent submits one construction record per argument using COPY, INFLECT, NORMALISE, ORDER, and DELETE, or reports a typed gap.

The server executes those operations and returns the passage and provenance. complete means construction succeeded. Checked wording is labelled 100%; unchecked transformations are Unverified and block selection. These labels describe derivation from the supplied fragments, whose authorship is assumed. Human review remains required.

Case and punctuation changes are checked. Nontrivial inflections and declared spelling replacements remain unverified until narrower rules are implemented.

Optional agent diagnostics record causal gaps and source contradictions with exact basis spans. The core does not detect them or certify preserved meaning.

Minimal candidate request:

{
  "passage_plan": {
    "passage_id": "p1", "claim": "Workers organise.",
    "arguments": [{"id": "a1", "claim": "Workers organise."}]
  },
  "fragments": [{"id": "user-1", "text": "Workers organise."}],
  "candidate": {"records": [{
    "argument_id": "a1",
    "operations": [{
      "type": "COPY", "fragment_id": "user-1", "text": "Workers organise."
    }]
  }]}
}

The synthesis record schema is 2.0; explicit 1.0 records are rejected. DELETE now edits a target piece; ORDER applies a permutation. Semantic support fields are replaced by optional diagnostics.verify_synthesis retains its legacy 1.0 flat derivation contract.

Related MCP server: clearon-source-audit

Run

uvx --from git+https://github.com/AhmedKishki/mcp-white-box-synthesis white-box-synthesis

For local development:

uvx --from . white-box-synthesis
python3 tests/test_synthesis.py
python3 tests/test_verify.py

See ROADMAP.md for the remaining work.

Available Tools

1 tool
verify_synthesisA

Verify a white-box-synthesis derivation, or record a declared gap.

Checks that every character of the output traces to a declared operation on a declared source span. Does not check meaning: that is the human's job.

Args: passages: Source passages. Each needs id and text, and should carry a source citation label, which flows through to the report. output_context: What the output passage is meant to support. candidate: {"output": str, "operations": [...]}. Each operation needs type (COPY, INFLECT, NORMALISE, DELETE or ORDER), passage_id, text quoted verbatim from that passage, and occurrence (1-indexed). INFLECT and NORMALISE also need output_text, and INFLECT needs axis (tense, number, case, article or pronoun). DELETE and ORDER accept an optional note. gap: A typed gap when no legal derivation exists. Needs type (one of the six gap types), passage_id, argument_id, missing_requirement, authoritative_owner, question and resolution_paths. Submit exactly one of candidate or gap.

Returns: A report with an overall status of accepted, rejected or gap, a per-operation verdict of verified, unverified or failed, the reconstruction result, counts, and a compact provenance declaration. Operations marked unverified are recorded claims rather than checked facts, and any derivation containing one declares Human wording: Unverified.

Inputs: passages (required), output_context (required), gap, candidate. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool, there is no possibility of confusing it with another. The purpose is clear and distinct.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern ('verify_synthesis'). Since there is only one tool, the naming convention is internally consistent.

    Tool Count4/5

    One tool is slightly below the typical 3-15 range, but it fits the server's narrow, single-purpose scope of verifying synthesis derivations. The tool is substantial and not redundant.

    Completeness4/5

    The tool covers the core verification workflow, including accepting passages, candidates, and gap declarations. It does not include auxiliary operations like retrieving past reports, but those are not clearly required for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to verify their own output mid-task by checking every claim against provided sources, returning supported, partial, unsupported, or contradicted verdicts with exact citations.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables revision-bound source audits with exact article fingerprinting, claim-to-source mapping, quotation verification, and immutable JSON evidence reports for prepublication review.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to verify citations and bibliographies and to check whether source documents support factual claims, using local inference, exact evidence provenance, and deterministic verdicts.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to verify whether a quoted passage appears word for word in a cited URL, DOI, or PubMed source, returning a verdict, similarity score, and character span so quotations can be validated before use.
      35 PyPI
      MIT