Skip to main content
Glama

claude_request

Destructive

Run Claude Code CLI requests synchronously, auto-deferring to pollable async jobs when the sync deadline is exceeded. Start by providing a prompt or structured prompt parts.

Instructions

Run a Claude Code CLI request synchronously (when async jobs are enabled, auto-defers to a pollable job past the sync deadline; otherwise runs to completion). Requires exactly one of prompt or promptParts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bareNoClaude --bare: minimal mode (skip hooks, LSP, plugin sync, attribution, auto-memory, keychain reads, CLAUDE.md auto-discovery). Under mcp_managed, this repository-rule suppression requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
nameNoClaude --name: display name for this session (shown in pickers/titles).
agentNoClaude --agent: dispatch to a named single sub-agent.
debugNoClaude -d/--debug: enable debug mode. true emits a bare --debug; a string emits --debug <filter> (e.g. "api,hooks"). Debug output goes to stderr only.
modelNoModel name or alias (e.g. sonnet, claude-sonnet-4-5-20250929, latest)
toolsNoClaude --tools: restrict the available built-in tool set (distinct from allowedTools permission gating). Pass [""] to disable all tools.
addDirNoClaude --add-dir: additional directories the CLI is allowed to read/write beyond the process cwd. Each entry is emitted as its own --add-dir instance. Under mcp_managed, non-empty addDir requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1. Stdio/local callers may pass local paths directly. Remote HTTP/OAuth callers must use relative paths inside a selected registered workspace. Do not call workspace_* tools to fix stdio/local provider path access.
agentsNoClaude --agents: inline JSON map of agent name → { description, prompt, tools?, model? }.
effortNoClaude --effort: low|medium|high|xhigh|max.
promptNoPrompt text for Claude (mutually exclusive with promptParts)
maxTurnsNoClaude --max-turns: cap on agent loop iterations.
safeModeNoClaude --safe-mode: start with all customizations (CLAUDE.md, skills, plugins, hooks, MCP, commands, agents) disabled for troubleshooting. Under mcp_managed, this repository-rule suppression requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
settingsNoClaude --settings: path to a settings JSON file or a JSON literal of additional settings. Powerful: settings can define hooks/permissions/model; passed verbatim.
worktreeNoSlice λ: run this request inside a dedicated git worktree owned by the gateway. `true` creates a fresh worktree at `<repoRoot>/.worktrees/<uuid>` branched from HEAD. `{ name?, ref? }` lets the caller supply a sanitized name and/or a git ref (default: HEAD). When the request carries a sessionId and the session already has a worktree, reuse requires same-host ownership metadata and a matching live Git registration. Named path collisions never reuse manager state. Gateway-managed worktrees require the local file-backed session manager and fail closed with PostgreSQL sessions. The Grok, Devin, and Mistral adapters require an explicit provider-native sessionId; fresh, createNewSession, and resumeLatest-only worktree requests fail closed because they cannot durably reselect the worktree. The request must select a registered workspace explicitly, through caller-owned session metadata, or through the configured default. Worktrees never fall back to the gateway process cwd and cannot be combined with local workingDir, addDir, or includeDirs paths. The gateway spawns the child CLI with `cwd: <worktree-path>`; no `-w`/`--worktree` flag is ever emitted to the underlying CLI. On worktree materialization, the gateway suppresses repository, system, and global Git hooks and configured clean, smudge, and process checkout filters, sparse checkout, and lazy object fetching. Filter-dependent content such as Git LFS remains in its repository representation instead of executing host commands. On session_delete or TTL eviction the gateway hides the session and runs `git worktree remove --force`. Failed removal retains a durable cleanup-pending tombstone which blocks reuse and is retried when the file store is registered on the owning host. The tombstone is finalized only after verified Git removal. Successful responses are prefixed with `[gateway] worktree=<absolute-path>\n` so callers can use the path. For Claude approvalStrategy:mcp_managed, requesting or reusing a worktree requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1. Other adapters reject mcp_managed before launch. NOTE: callers should `.gitignore` the `.worktrees/` directory in their repo (the gateway does NOT auto-gitignore; see slice λ spec Q4).
debugFileNoClaude --debug-file: write debug logs to a specific file path (enables debug mode).
pluginDirNoClaude --plugin-dir: load a plugin from a directory or .zip for this session only. One --plugin-dir instance per entry.
pluginUrlNoClaude --plugin-url: load a plugin .zip from a URL for this session only. One --plugin-url instance per entry.
sessionIdNoOn a fresh request this id is emitted as Claude --session-id <uuid> (must be a valid UUID that does not already exist). Resume the latest cwd conversation with continueSession:true. gw-* ids are not valid Claude --session-id values.
workspaceNoRegistered workspace alias for remote HTTP/OAuth provider calls. Do not use this field, workspace_list, or workspace_register_existing_repo as a fallback for stdio/local provider path access; pass workingDir/addDir/includeDirs directly instead.
jsonSchemaNoClaude --json-schema: JSON Schema literal (NOT a path) constraining structured output. Object values are JSON.stringify-d; string values are passed verbatim. Use with outputFormat='json'. Set outputFormat:json so the gateway treats the reply as structured output (skips response optimization and warning injection); the default output format is not json, so pass it explicitly.
mcpServersNoMCP servers exposed to Claude
workingDirNoClaude process working directory. The gateway launches Claude in this directory. Stdio/local callers may pass local paths directly. Remote HTTP/OAuth callers must use relative paths inside a selected registered workspace. Do not call workspace_* tools to fix stdio/local provider path access.
forkSessionNoClaude --fork-session: branch from an existing session into a fresh fork.
promptPartsNoCache-aware structured prompt: { system?, tools?, context?, task, cacheControl? }. Use for repeated calls that share a stable prefix — `system`/`tools`/`context` are the stable head; `task` is the volatile tail (never marked). Set `cacheControl: { system?: boolean, tools?: boolean, context?: boolean }` to opt into explicit Anthropic prefix caching via `--input-format stream-json` (slice κ). Requires `outputFormat: 'stream-json'` and hard-codes `ttl='1h'` (Anthropic rejects 5m blocks after Claude Code's 1h-marked session-wrap content). Mutually exclusive with `prompt`. The stable prefix hash is logged to the flight recorder for cache_state aggregates.
allowedToolsNoAllowed tools (['Bash(git:*)','Edit','Write'])
forceRefreshNoBypass dedup and force a fresh CLI run even if a recent identical request exists
maxBudgetUsdNoClaude --max-budget-usd: spend cap for this request in USD.
outputFormatNoOutput format (text|json|stream-json). DEFAULT: stream-json; the gateway parses NDJSON usage events to extract input/output/cache_read/cache_creation tokens + cost + model, persists them to the flight recorder for cache_state aggregates, and still returns the assistant text. Override to 'text' only when you truly want unparsed stdout (loses observability).stream-json
systemPromptNoClaude --system-prompt: replace the system prompt entirely. Mutually exclusive with appendSystemPrompt. Under mcp_managed, an override requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
correlationIdNoRequest trace ID (auto if omitted)
fallbackModelNoClaude --fallback-model: model name to auto-fallback to when the default model is overloaded (effective only with --print, which the gateway always uses).
idleTimeoutMsNoIdle timeout in ms (min 30s, max 1h, omit=CLI default). Idle enforcement applies only when outputFormat is stream-json; it is ignored for text/json.
providerFlagsNoFlags passed to the provider binary verbatim, keyed exactly as the binary spells them (e.g. {"--best-of-n": "3", "--verbatim": true, "--rules": ["a", "b"]}). Use this for any flag your installed CLI accepts that this schema does not name: the binary decides what it supports, not the gateway. true emits the flag alone; a list REPEATS the flag once per item (pass a joined string if your CLI wants a comma-separated value). Values may not start with '-', and a flag the gateway is already emitting for this request is refused rather than duplicated. LOCAL stdio callers only: remote HTTP/OAuth callers are refused every flag here and should use this tool's declared parameters, which carry their own host-path and approval gates.
approvalPolicyNoApproval policy when approvalStrategy is mcp_managed: strict|balanced|permissive (default balanced). Ignored under legacy strategy.
optimizePromptNoOptimize prompt before execution
permissionModeNoClaude --permission-mode: default|acceptEdits|auto|bypassPermissions|manual|dontAsk|plan. `default` is a no-op (no flag emitted). Under mcp_managed, bypassPermissions requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
settingSourcesNoClaude --setting-sources: comma-separated setting sources to load (user|project|local) for reproducible/isolated headless runs.
continueSessionNoContinue the most recent Claude conversation in the selected workspace (emits --continue; real CLI continuity). Stable workspace selection is required via workingDir, a registered workspace, or the configured default workspace.
disallowedToolsNoDisallowed tools
strictMcpConfigNoRestrict Claude to provided MCP config only. mcp_managed always enforces this isolation, even when false is supplied.
approvalStrategyNoApproval strategy: legacy (default) lets Claude's own flags decide; mcp_managed routes the run through the gateway approval gate and uses acceptEdits by default. An explicit bypassPermissions request requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.legacy
compressResponseNoCompress the response display text via the native compressor (default: [compression].enabled in config.toml, off unless opted in). Skipped for structured output.
createNewSessionNoForce new session
optimizeResponseNoOptimize response output
systemPromptFileNoClaude --system-prompt-file: replace the system prompt from a file path (path variant of systemPrompt).
includeHookEventsNoClaude --include-hook-events: include all hook lifecycle events in the output stream. Only takes effect with outputFormat=stream-json (the default).
appendSystemPromptNoClaude --append-system-prompt: append to the existing system prompt. Mutually exclusive with systemPrompt. Under mcp_managed, an override requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
replayUserMessagesNoClaude --replay-user-messages: re-emit user messages from stdin back on stdout for acknowledgment. Only works with input-format=stream-json and outputFormat=stream-json (the cacheControl path).
requestInstructionsNoPer-request Kit instructions. Available only when [personal_config].enabled = true.
noSessionPersistenceNoClaude --no-session-persistence: do not write this session to disk (ephemeral one-shot runs; mirrors codex --ephemeral).
appendSystemPromptFileNoClaude --append-system-prompt-file: append a system prompt from a file path (path variant of appendSystemPrompt).
dangerouslySkipPermissionsNoDEPRECATED: prefer `permissionMode: "bypassPermissions"`. Maps to it when `permissionMode` is unset. Under mcp_managed, either form requires approval and LLM_GATEWAY_APPROVAL_ALLOW_BYPASS=1.
excludeDynamicSystemPromptSectionsNoClaude --exclude-dynamic-system-prompt-sections: trim dynamic context blocks from the system prompt.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv3.2.0
  2. Removedv3.0.0
  3. First observedv2.16.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the bar for behavioral disclosure is lower. The description adds genuinely useful context beyond annotations: synchronous execution model, deferral to a pollable job past the sync deadline, and the prompt/promptParts exclusivity requirement. No contradiction with annotations.

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

Conciseness5/5

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

One dense sentence with zero waste: primary behavior front-loaded, deferral logic in the parenthetical, and the key constraint at the end. Every clause earns its place, and the critical usage facts are all present despite the 53-parameter schema beneath.

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

Completeness3/5

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

For a tool this complex (53 params, approval gates, worktree semantics, no output schema), the description itself is thin — it does not describe the response shape or return-value semantics. However, the outputFormat parameter in the schema documents the return behavior (stream-json parsing, usage events, observability), and the 100% schema coverage carries the burden. Adequate for correct invocation, with return-value details left to the schema.

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% with exceptionally detailed parameter docs (e.g., worktree, providerFlags, outputFormat), so the baseline of 3 applies and the description need not compensate. The only param guidance in the description — 'Requires exactly one of prompt or promptParts' — is redundant with the schema's own mutual-exclusivity note on prompt.

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

Purpose5/5

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

States a specific verb and resource ('Run a Claude Code CLI request synchronously') and clearly differentiates from sibling claude_request_async by describing the sync execution model and auto-deferral behavior. The exclusivity constraint on prompt/promptParts adds further precision. An agent can immediately tell this apart from the async variant and from codex_request/gemini_request etc.

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

Usage Guidelines4/5

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

The description conveys when the sync behavior applies and when the call auto-defers to a pollable job ('when async jobs are enabled... otherwise runs to completion'), which is the key operational decision for this tool. It does not explicitly name claude_request_async as the alternative for long-running work, so the routing guidance is implicit rather than explicit, but the context is clear.

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

Latest Blog Posts

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/verivus-oss/llm-cli-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server