Skip to main content
Glama
AhmedKishki

white-box-synthesis

by AhmedKishki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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
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.

Prompts

Interactive templates invoked by user choice

NameDescription
white_box_synthesis_processThe white-box-synthesis process. Read before attempting a synthesis.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

ActivityMaintained
ResponsivenessNo issues

Resources