Schema | Ploidy

Ploidy

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`PLOIDY_PORT`	No	Server port	8765
`PLOIDY_API_KEY`	No	Optional API key for auto mode
`PLOIDY_DB_PATH`	No	Database location	~/.ploidy/ploidy.db
`PLOIDY_API_MODEL`	No	Optional model override for auto mode	gpt-5.4
`PLOIDY_LOG_LEVEL`	No	Logging level	INFO
`PLOIDY_AUTH_TOKEN`	No	Bearer token auth (optional)
`PLOIDY_API_BASE_URL`	No	Optional auto-debate backend	https://api.openai.com/v1

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

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name	Description
debateA	Run a context-asymmetric debate in a single call. One canonical entry point. Pick a mode: `auto` (default): Ploidy generates both sides via the configured OpenAI-compatible API endpoint and returns the convergence result. Requires non-empty `context_documents` plus a configured API endpoint. HITL pause/resume is available via `pause_at`; resume with the legacy `debate_review` tool. `solo`: you supply both positions (and optionally both challenges) and Ploidy persists + converges them. No external API key needed — the recommended single-terminal flow when the caller (e.g. Claude Code itself) writes both sides locally. The older 12-tool surface (`debate_start` / `debate_join` / `debate_position` / ...) remains available for two-terminal and HITL workflows but is now deprecated; new integrations should use this tool. Args: prompt: The decision question to debate. mode: `"auto"` or `"solo"`. deep_position: (solo only) Deep side's stance. fresh_position: (solo only) Fresh side's stance. deep_challenge: (solo only) Optional deep-side critique. fresh_challenge: (solo only) Optional fresh-side critique. deep_label / fresh_label: (solo) display labels for roles. fresh_role: (auto) `"fresh"` or `"semi_fresh"`. delivery_mode: (auto + semi_fresh) `"passive"`, `"active"`, or `"selective"`. pause_at: (auto) Optional `"challenge"` or `"convergence"` HITL pause point. deep_n / fresh_n: (auto) Ploidy level per side. effort: (auto) `"low"`, `"medium"`, `"high"`, `"max"`. injection_mode: (auto) Context formatting mode. context_pct: (auto) Percentage of context to retain. language: (auto) Output language code. deep_model / fresh_model: (auto) Model override. Supplying either applies it to both sides; if both are supplied they must match. context_documents: Documents attached only to the Deep side. Required and non-empty in auto mode; optional provenance in solo mode. context_sources: Optional provenance labels, one per context document. blocked_sources: Optional strings that must not appear in source labels or context documents. target_lease: Optional target identifier that pins this debate's scope. allowed_sources: Optional source-label allowlist; defaults to target_lease when a target lease is set. Returns: Convergence result dict, or paused state (auto + pause_at).
debate_startA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Begin a new debate session with a decision prompt.` Creates a debate and a Deep (full-context) session. Share the returned debate_id with the fresh session so it can join.
debate_joinA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Join an existing debate as a fresh or semi-fresh session.`
debate_positionA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Submit a position from a session.`
debate_challengeA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Submit a challenge to another session's position.`
debate_convergeA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Trigger convergence analysis for a debate.`
debate_cancelA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Cancel a debate in progress.`
debate_deleteA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Permanently delete a debate and all its data.`
debate_statusA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Get current state of a debate.`
debate_historyA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Retrieve past debates and their outcomes.`
debate_soloA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Run a complete debate from caller-supplied positions in one call.` Single-terminal entry point: the caller generates both sides locally and submits the texts here. No external API key required.
debate_autoA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Run a complete debate automatically in a single command.` Requires non-empty `context_documents` and a configured API endpoint. Generates positions and one independent challenge per seat with one resolved model, runs the protocol, and returns the convergence result.
debate_reviewA	DEPRECATED (v0.4) — prefer `debate(prompt, mode=...)`. `Review and resume a paused auto-debate (HITL).` Call after `debate_auto` with `pause_at` paused the run. Action is one of 'approve', 'override', or 'reject'.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
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

A3.9/5.0

Scored 2026-08-05 06:55 across 13 tools

Disambiguation4/5

The set includes one canonical tool and 12 deprecated tools that are explicitly marked as superseded. While each deprecated tool has a distinct action, they overlap with the canonical tool's modes, so an agent must read the deprecation notices carefully. The guidance is clear, so most ambiguity is resolved.

Naming Consistency4/5

The deprecated tools follow a consistent 'debate_' prefix with verb suffixes, but the canonical 'debate' and two mode-based tools ('debate_solo', 'debate_auto') deviate from the verb pattern. Overall the consistency is good, with only minor deviations.

Tool Count2/5

The tool count is bloated: 12 of 13 tools are deprecated legacy surface, while the entire functionality is available through the single 'debate' tool. This duplication inflates the count unnecessarily, making the set feel much heavier than its actual scope.

Completeness5/5

The debate lifecycle is fully covered: starting, joining, submitting positions, challenging, converging, canceling, deleting, status, history, and HITL review. The canonical tool subsumes all of these, so there are no obvious gaps.

Maintenance

ActivityStale

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Related Servers