PCQ
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_projectA | Resolve cq.yaml + CQ_CONFIG_JSON env into a single ResolvedConfig view. Returns project_root, cq_yaml_path, name, cmd, cfg, declared_metrics, output_dir. Read-only — does not create directories or mutate state. |
| inspect_projectA | Return project structure, entrypoint kind, contract state, and output evidence. Read-only. |
| validate_projectB | Run static and contract validation before execution. Optional inline ExperimentPlan / ExperimentPlanSet validation. Read-only. |
| validate_runB | Run post-run validation gates (manifest / metrics / run_summary) on a completed output directory. Read-only. |
| describe_runA | Return a compact, decision-facts oriented summary of a RunRecord. Includes best/last metrics, validation status, lineage, artifact counts, decision_facts. Read-only. |
| compare_runsA | Diff two RunRecords (or output dirs). Returns metric deltas, config changes, lineage relation, decision_facts. Read-only. |
| lineage_chainC | Walk a RunRecord's parent chain. Returns ordered nodes from this run back to its earliest reachable ancestor. Read-only. |
| apply_planA | Apply ExperimentPlan to project (modifies cq.yaml.configs only — never train.py). Provenance recorded under .pcq/plans/.json. Returns rejected envelope with reason='schema_invalid'|'validation_failed' on bad input. |
| apply_plansetA | Expand ExperimentPlanSet members into N output directories, each with its own cq.yaml + plan provenance. Returns rejected envelope with reason='schema_invalid'|'validation_failed' on bad input. |
| init_experimentB | Scaffold a CQ-runnable experiment (cq.yaml + train.py contract script, optionally pyproject.toml + agent runtime assets). |
| finalize_runB | Generate run_record.json + validation_report.json for an output directory. Walks ancestors to find project root if not provided. Writes to output_dir. |
| agent_installB | Install pcq agent runtime assets (AGENTS.md / CLAUDE.md managed block, .agents|.claude/skills/pcq/SKILL.md). Optionally write .mcp.json to wire pcq MCP server. |
| agent_statusA | Inspect pcq agent runtime asset status (installed / missing / stale / divergent / unmanaged) without writing. Read-only. |
| run_experimentA | Execute cq.yaml.cmd with auto-wired CQ_CONFIG_JSON env. Captures stdout/stderr to .pcq/run_*.log. For long-running GPU training, prefer the CQ service queue. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/playidea-lab/pcq'
If you have feedback or need assistance with the MCP directory API, please join our Discord server