Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM
86
88%
Does it follow best practices?
Impact
86%
1.86xAverage score across 45 eval scenarios
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent produces a buildable MCP wiring — three concerns the call shape alone doesn't catch: (1) the transport builder is a top-level extension on `McpToolRegistryProvider` and needs its own import alongside the provider; (2) `agents-mcp` publishes as `1.0.0-beta`, not `1.0.0`; (3) it publishes only JVM variants, so the artifact needs the `-jvm` suffix. Agents that copy the call shape from documentation without resolving these typically produce code that does not compile or a Gradle line that fails resolution.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Picks the SSE transport",
"description": "Builds the MCP registry using `McpToolRegistryProvider.fromSseUrl(...)` against the server URL. Does NOT use `streamableHttp` (the modern transport the operator said the server does not speak) or `fromProcess` (the server is not a local subprocess)",
"max_score": 18
},
{
"name": "Imports the `fromSseUrl` extension explicitly",
"description": "The produced file contains `import ai.koog.agents.mcp.fromSseUrl` (or a star-import covering the package) alongside `import ai.koog.agents.mcp.McpToolRegistryProvider`. Importing only the provider does NOT bring the transport extension into scope — `fromSseUrl` is a top-level extension function in the same package, declared separately from the provider object",
"max_score": 22
},
{
"name": "Pins the MCP artifact to `1.0.0-beta`",
"description": "The Gradle dependency uses version `1.0.0-beta` (e.g., `ai.koog:agents-mcp-jvm:1.0.0-beta`). NOT `1.0.0` — Koog 1.0's stable release did not publish `agents-mcp` at `1.0.0`; only `1.0.0-beta` is on Maven Central. An answer that pins `1.0.0` fails dependency resolution",
"max_score": 18
},
{
"name": "Uses the `-jvm` suffix on the artifact",
"description": "The Gradle line uses `ai.koog:agents-mcp-jvm:...` (NOT bare `ai.koog:agents-mcp:...`). `agents-mcp` publishes only JVM-specific variants at the relevant version; without the suffix Gradle KMP variant resolution cannot pick the JVM artifact and the build fails with 'could not find'",
"max_score": 18
},
{
"name": "Builds the registry before constructing the agent",
"description": "Calls `McpToolRegistryProvider.fromSseUrl(...)` and assigns it to a variable BEFORE the `AIAgent(...)` call, then passes that variable as `toolRegistry`. Does not try to add MCP tools after the agent is constructed (the registry is read once during feature install)",
"max_score": 14
},
{
"name": "Calls the suspending builder inside a coroutine context",
"description": "The `fromSseUrl` builder runs inside the existing `runBlocking { ... }` (or another coroutine scope), since it is a suspending call",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
scenario-45
skills
add-observability
add-persistence
add-rag
add-structured-output
add-token-budgeting
add-tool
cache-llm-calls
define-prompt
domain-model-subtask-pipeline
references
enable-prompt-caching
handle-agent-events
manage-state
migrate-from-0-x
model-planner-subtasks
persist-chat-history
query-sql-from-agent
scaffold-agent
snapshot-and-restore
test-koog-agents
trace-agent-internals
use-attachments
use-functional-agent
use-llm-node-variants
use-planner
wire-a2a
wire-acp-server
wire-ktor-server
wire-mcp-server
wire-spring-boot