Raw JSON Schema
Kast generates the four semantic tools’ input schemas and request examples from one authored contract. The links below point to that generated source, not a separate documentation schema.
The support callables have separate availability: direct MCP exposes
health_check; the hosted App Server exposes workspace_lifecycle. Their authoritative input and response definitions are in the generated OpenAPI document, under /callables/health_check and /callables/workspace_lifecycle. These labels are documentation identifiers, not HTTP endpoints.
These source links follow main, which can be ahead of an installed release. Use the catalog exposed by your installed integration as the authority for that release. Rediscover it after an upgrade rather than caching input assumptions indefinitely.
The authored schema contains shared definitions and tool metadata. The per-tool parameters.json files above are the generated request schemas to use when validating a tool’s arguments. $defs and $ref keep shared forms connected; do not flatten variants into an all-optional property bag.
Read a schema without reading every definition
Start at the tool’s required root properties. Forquery_symbols, select request and follow its action variant: RUN, RESUME, or READ_RESULT. For RUN, choose one source, add only the steps needed by the question, and choose the output form.
Defaulted fields do not need to appear in every example. Server admission supplies documented defaults and enforces semantic restrictions beyond JSON shape validation. Passing a JSON Schema check does not prove that a reference is current, a result is complete, or a mutation is permitted.
Samples and observed responses
The generated sample files contain valid-input examples and deliberately invalid examples for contract testing. Their opaque reference values are not reusable tokens from your session. They are not live semantic response recordings.Recorded walkthrough
Download the request/response recording for Find and trace code and Combine query results. It contains sixteen real Tool RPC calls, including their complete request and response payloads. Eachcalls entry records its ID, timestamp, tool, request, and response.
Captured on September 29, 2026 (UTC), using matched Kast CLI and IDEA plugin version 0.20260928.121700, IDEA/Kotlin build 262.10315.125. The checkout was 81fb023c06f8dba63e3531f49632f465b5cc6b21; its changes from the tutorials’ source revision 56df0912e46b182bb4ad8beabd1512823100fd72 were confined to docs/public. All successful and qualified calls retain the same host and epoch 7, with SAVED_PSI_COMMITTED content.
Only the machine’s absolute checkout prefix was normalized to
/workspace/kast. Opaque references, relationships between calls, host identity, epochs, offsets, and qualifications remain unchanged. The installed version predates verbose and returns detailed payloads; this recording does not demonstrate compact output.
To reproduce, start in the linked source checkout and pass a call’s request object to kast-tool-rpc-complete call query_symbols. Execute calls in order, substituting newly issued references for the recorded session’s tokens. Keep builds and source edits paused while composing retained results. Each run must establish its own counts and coverage; recorded handles are not reusable credentials or portable symbol identifiers.
The captures’ requests are checked against the generated input schema, their envelopes against ToolRpcReply, and their operation documents against the generated semantic-result schema. These shape checks complement the recorded native evidence; they do not replay IDEA.
Rendered contracts and transport details
Rendered contracts and transport details
The existing generated OpenAPI document remains available for complete request and response definitions. Its
POST /callables/... labels organize documentation; they are not HTTP endpoints.The native query reference renders the detailed query contract. Existing diagnostic, change, lifecycle, and model URLs remain available for compatibility, but are not part of the setup path.Client authors can read the MCP contract, Tool RPC contract, and compatibility notes. These explain transport wrappers and support-tool availability; ordinary users do not need them to connect an agent.