Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_models_apply_migration

Apply one model migration: replace a gone model with a new one in a global config key or an agent's model chain, enacting a discovered migration after review.

Instructions

Apply ONE model migration: replace a gone model with a new one in either a global config key or a per-agent model_chain. Exactly one of configKey / agentId must be given. This is the gated action behind the discovery cron's suggestions — nothing changes until you call it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "kernel_models_apply_migration"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesNew model id to use
fromYesModel id to replace (the gone one)
slugYesProvider slug of the model being replaced
agentIdNoAgent id whose model_chain to rewrite
configKeyNoGlobal config env key, e.g. AGENTS_EVAL_MODEL or AGENTS_DEFAULT_MODEL_CHAIN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.9/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 burden and does disclose the key mutation semantics: it is gated, nothing changes until invoked, and only one migration is applied per call. It does not state permission/auth requirements, whether the change is reversible, or what happens if `from` is no longer a gone model or both configKey and agentId are supplied.

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?

Two tightly written sentences with the operation and its scope front-loaded, followed by the exclusivity rule and the gating warning. Nothing is redundant or wasted.

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?

For a five-parameter mutation tool with no annotations and no output schema, the description covers what is mutated, the per-call scope, and the parameter exclusivity rule. It leaves unaddressed what the tool returns on success and how failures (e.g., a model that isn't gone) surface, which an agent calling a write tool would want to know.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning the schema cannot express — the XOR constraint that exactly one of configKey / agentId must be given, and that a single call applies only one migration. It does not clarify how slug relates to from/to, which would be the remaining gap.

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 names a specific verb and resource ("Apply ONE model migration") and states the actual effect: replacing a gone model with a new one in either a global config key or a per-agent model_chain. It also positions the tool relative to the discovery cron's suggestions, so an agent can tell it apart from a read-only discovery tool, though it never names the sibling that produces those suggestions.

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?

It gives a clear conditional constraint — exactly one of configKey / agentId — and explains the workflow context (this is the gated action behind the discovery cron, nothing changes until you call it). What's missing is explicit when-not guidance, e.g., what to do if no pending migration was suggested or how to choose between configKey and agentId beyond mutual exclusivity.

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

Deploy Server

Other Tools