Skip to main content
Glama

roast

Generate multi-perspective adversarial feedback on code, architecture, and ideas using parallel AI critics to uncover blind spots.

Instructions

Unified brutal AI critique delivered by a multi-critic panel running in parallel. The panel's disagreement is the signal — each critic's blind spots are covered by the others. Specify domain for targeted analysis. Consolidates all roast_* tools into one polymorphic API. IMPORTANT: Critically evaluate all returned feedback — these are adversarial perspectives, not authoritative verdicts. Weigh each claim against evidence before presenting to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slaNoSLA for infrastructure
urlNoLive URL for visual evaluation (e.g., 'http://localhost:5173'). When provided with design domain, critics use Playwright to navigate and visually evaluate the running interface. Strongly recommended for design critiques.
clisNoSubset of native critics to run. [] = run ONLY the named clients[] (no default critics); omit to run all available.
dataNoData for research
brandNoBrand identity or design system constraints for design domain
depthNoMax depth for file_structure
fieldNoField for research
limitNoMax chars/chunk
scaleNoScale for architecture/infrastructure
usersNoUsers for product
assetsNoAssets for security
budgetNoBudget for infrastructure
claimsNoClaims for research
cursorNoPagination cursor
domainYesAnalysis domain
mediumNoDesign medium for design domain (web, mobile, spatial, print)
modelsNoPer-CLI model override. Claude honors overrides. Codex uses the Codex CLI configured/default model by default; set BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE=true to allow a codex override. Agy accepts a human-readable label ("Gemini 3.1 Pro (High)", "Claude Sonnet 4.6 (Thinking)", etc.) via its native --model flag (1.0.10+); Pro/Claude/GPT-OSS tiers require Antigravity entitlement. Omit to use each CLI's configured default.
offsetNoPagination offset
resumeNoContinue conversation with a new prompt; omit for pagination/page reads
targetYesFilesystem path to analyze (e.g., '/path/to/project' or '.'). Directs agents to the relevant part of the codebase.
clientsNoNamed CLI clients to run, ADDITIVE to the native critics (use clis:[] to run ONLY these). Allows multiple isolated Claude Code clients (up to 16), including custom Anthropic-compatible endpoints, in one roast.
contextNoEssential context for the critique. For abstract domains (idea, architecture, security, etc.), this is the primary input describing what to evaluate. For filesystem domains, provides supplementary background (e.g., goals, constraints, team context).
metricsNoMetrics for product
postureNoProcedural posture or use context for legal domain (e.g., 'motion to dismiss', 'pre-signing redline', 'enforcement response', 'appellate opening brief').
verboseNoDetailed output
audienceNoTarget audience for design domain
practiceNoPractice register for legal domain — freeform (e.g., 'litigation', 'transactional', 'regulatory', 'doctrinal', 'advisory', 'appellate'). Modulates the critic's adversary geometry.
timelineNoTimeline for idea
resourcesNoResources for idea
complianceNoCompliance for security
context_idNoContext ID for cached pagination or conversation continuation
deploymentNoDeployment for architecture
commitRangeNoCommit range for git_history
competitionNoCompetition for product
constraintsNoConstraints for architecture
mcp_serversNoMCP servers to enable for CLI agents (e.g., ["playwright"]). Enables evidence-backed analysis via external tools. Available: playwright. Auto-enabled for design domain.
runCoverageNoRun coverage for test_coverage
threatModelNoThreat model for security
jurisdictionNoGoverning jurisdiction or forum for legal domain (e.g., 'US federal', 'NY state', '9th Cir.', 'Delaware Chancery', 'EU').
force_refreshNoIgnore cache
includeDevDepsNoInclude dev deps for dependencies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.10
  2. Removedv1.18.9
  3. Changed4 schema fields changedv1.18.3
    • addedInput schema / properties / clients
      Added value: +{
      +  "description": "Named CLI clients to run, ADDITIVE to the native critics (use clis:[] to run ONLY these). Allows multiple isolated Claude Code clients (up to 16), including custom Anthropic-compatible endpoints, in one roast.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "authToken": {
      +        "description": "Bearer token for ANTHROPIC_AUTH_TOKEN. Prefer authTokenEnv for shared configs.",
      +        "type": "string"
      +      },
      +      "authTokenEnv": {
      +        "description": "Environment variable name containing the bearer token.",
      +        "type": "string"
      +      },
      +      "baseUrl": {
      +        "description": "Claude-compatible endpoint base URL for ANTHROPIC_BASE_URL (http(s) only). Presence marks the client 'routed': isolated from native credentials and hardened (no web egress/MCP) by default.",
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "configDir": {
      +        "description": "Per-client CLAUDE_CONFIG_DIR for Claude Code state isolation. Defaults to ~/.brutalist/claude-clients/<id> for routed clients.",
      +        "type": "string"
      +      },
      +      "containment": {
      +        "description": "Tool/sandbox policy. 'hardened' (DEFAULT for any routed/custom-endpoint client) additionally denies WebFetch, WebSearch, and all MCP servers. 'standard' restores the native tool surface — only for an endpoint you fully trust.",
      +        "enum": [
      +          "hardened",
      +          "standard"
      +        ],
      +        "type": "string"
      +      },
      +      "env": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "description": "Additional per-client environment variables (applied last; override resolved values).",
      +        "type": "object"
      +      },
      +      "id": {
      +        "description": "Stable display id for this CLI client, e.g. claude-native or glm.",
      +        "maxLength": 80,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "includeProcessAuth": {
      +        "description": "Routed clients are isolated by default (no native Claude credentials). Set true to ALSO inherit the process ANTHROPIC_API_KEY/CLAUDE_CODE_OAUTH_TOKEN into this client; set false to force isolation on an otherwise-native client.",
      +        "type": "boolean"
      +      },
      +      "mcpServers": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "model": {
      +        "description": "Per-client model override.",
      +        "type": "string"
      +      },
      +      "provider": {
      +        "default": "claude",
      +        "description": "Underlying CLI provider.",
      +        "enum": [
      +          "claude",
      +          "codex",
      +          "agy"
      +        ],
      +        "type": "string"
      +      },
      +      "smallFastModel": {
      +        "description": "Claude Code small/fast model override for ANTHROPIC_SMALL_FAST_MODEL. Defaults to `model` for routed clients so a gateway never sees Claude's built-in haiku name.",
      +        "type": "string"
      +      },
      +      "timeout": {
      +        "exclusiveMinimum": 0,
      +        "type": "integer"
      +      },
      +      "workingDirectory": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
    • changedInput schema / properties / clis / description
      Previous value: -"Subset of critics to run."New value: +"Subset of native critics to run. [] = run ONLY the named clients[] (no default critics); omit to run all available."
    • changedInput schema / properties / clis / minItems
      Previous value: -1New value: +0
    • changedInput schema / properties / models / description
      Previous value: -"Per-CLI model override. Claude honors overrides. Codex uses the Codex CLI configured/default model by default; set BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE=true to allow a codex override. Agy accepts a human-readable label (\"Gemini 3.1 Pro (High)\", \"Claude Sonnet 4.6 (Thinking)\", etc.) via settings.json swap under flock(2); Pro/Claude/GPT-OSS tiers require Antigravity entitlement. Omit to use each CLI's configured default."New value: +"Per-CLI model override. Claude honors overrides. Codex uses the Codex CLI configured/default model by default; set BRUTALIST_CODEX_ALLOW_MODEL_OVERRIDE=true to allow a codex override. Agy accepts a human-readable label (\"Gemini 3.1 Pro (High)\", \"Claude Sonnet 4.6 (Thinking)\", etc.) via its native --model flag (1.0.10+); Pro/Claude/GPT-OSS tiers require Antigravity entitlement. Omit to use each CLI's configured default."
  4. First observedv1.14.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It helpfully discloses that critics run in parallel, that their disagreement is the signal, and that output is adversarial feedback to be weighed rather than authoritative — useful output-nature context. But it omits operational traits the 41-param surface implies: latency/cost of spawning up to 16 clients plus native critics, and the fact that agents have Bash/WebFetch/WebSearch access.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core purpose, followed by the key behavioral caveat about evaluating adversarial output. Efficient and well-ordered, with only mild redundancy in the consolidation and evaluation-caveat lines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does convey the nature of the return (panel disagreement, adversarial perspectives) and how to treat it, which is the main return-value guidance needed. It is thin on navigating the 41-parameter surface, but with 100% schema coverage that burden is largely offloaded. Adequate overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents all 41 parameters in depth. The description adds only the marginal note that domain drives targeted analysis, plus schema-level detail elsewhere. No compensating value beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb+resource: a unified AI critique produced by a multi-critic panel running in parallel, and notes it consolidates all roast_* tools into one polymorphic API. It implicitly distinguishes itself from the debate-style sibling ('running in parallel'), though it does not name roast_cli_debate or the discover/roster siblings. Clear purpose, but sibling differentiation is only suggestive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says to 'specify domain for targeted analysis' and advises critically evaluating returned feedback, which implies usage context. However, it never states when to choose this tool over roast_cli_debate, brutalist_discover, or cli_agent_roster, nor any prerequisites. Usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.