critique_against_corpus

Inputs

{
  "type": "object",
  "properties": {
    "workspace_id": {
      "type": "string"
    },
    "draft_text": {
      "type": "string"
    },
    "findings": {
      "type": "object"
    },
    "mode": {
      "type": "string",
      "enum": [
        "agent",
        "byo_key"
      ]
    }
  },
  "additionalProperties": false,
  "required": [
    "workspace_id",
    "draft_text"
  ]
}

Outputs and behavior

Prepare workspace grounding for a draft critique, or append your agent's findings to its critique log. Use after assemble_workspace; use get_workspace to read earlier critiques or revise_script to save a script revision. Omit findings to retrieve context, then submit your analysis with findings. Repeated submissions append log entries. Server-side BYO generation is not implemented; the agent performs the analysis.

The registry does not publish an output schema for this tool. The description above is its documented behavior; response fields beyond it are not specified here.

Example call

Example tool name and arguments, generated from the input schema. Replace placeholder strings and sample numbers with your own values. This is a request template, not a recorded call or response.

{
  "name": "critique_against_corpus",
  "arguments": {
    "workspace_id": "YOUR_WORKSPACE_ID",
    "draft_text": "YOUR_DRAFT_TEXT"
  }
}

Clients

This tool is available to MCP clients using stdio or http.

The registry records transport support, not individual client test results. See the MCP setup reference for named clients, configuration, and tool-list limits.