Loading ToolBench
Model Context Protocol (MCP) adapter for ForkFlux, enabling AI coding assistants to securely publish and claim jobs.
ForkFlux MCP demonstrates solid tool design with clear naming conventions (verb_noun pattern: create_job, list_jobs, claim_job) and comprehensive parameter schemas. All 8 tools have descriptions and typed input schemas with enums for constrained values (JobStatusEnum, JobPriorityEnum, TargetRoleEnum). However, output schemas are not documented, LLMs cannot predict response structure for downstream chaining. Error handling guidance is absent; tools lack recovery hints. Parameter descriptions are present but generic (e.g., 'The ID of the job to update' lacks context on when/why). Complex nested types (JobArtifact, RoutingRule) are referenced but not defined in visible schema. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear read/write semantics.
Updates the status of a claimed job (e.g., mark as completed, failed, blocked, or cancelled).
Claims a specific job by ID for the current agent.
Claims the highest-priority available job for a specific target role.
Publishes a new handoff job to the ForkFlux collaboration bus for delegation.
Retrieves focused rejection metadata for a retry job before execution.
Lists available jobs from the ForkFlux collaboration bus with optional filtering.
Output schemas not documented. LLMs cannot predict response structure, breaking tool chaining. forkflux_create_job should document returned job_id, status, created_at; forkflux_list_jobs should document pagination fields and per-job structure.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). forkflux_create_job, forkflux_claim_job, forkflux_change_job_status, forkflux_update_job, forkflux_reject_job are destructive but unmarked. Agents cannot distinguish safe from risky operations.
Complex nested types (JobArtifact, RoutingRule) referenced in schemas but not defined. LLMs cannot construct valid nested payloads without seeing the schema for these types. Define inline or reference external schema definitions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2026-07-28+ | v2 |
Rejects a completed job and creates a linked retry iteration with a specific rejection reason.
Updates the mutable context_payload or constraints of a published handoff job.
No error handling guidance. Tools lack recovery hints (e.g., 'Job not found. Call forkflux_list_jobs to find available jobs.'). Agents cannot self-correct on failures.
Parameter descriptions lack context. 'The ID of the job to update' does not explain when to use forkflux_update_job vs forkflux_change_job_status. Descriptions should state WHAT the tool does, WHEN to use it, and prerequisites.