Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

activate_license

Read-only

Provides sign-in instructions when an old script or agent supplies a retired license key, explaining that Kiln access now comes through account sign-in.

Instructions

Retired: license keys no longer unlock Kiln. Sign in instead.

Kiln stopped taking license keys on 2026-11-01; a plan reaches a machine
only through the Kiln account it is signed in to.  This tool saves
nothing and reads nothing it is sent: it answers with the sign-in steps,
so an agent or an old script that still calls it learns the way in.
Show the user ``error`` as written, then sign them in (``kiln_signin``).

Args:
    key: Ignored.  Kept so an older call still gets this answer.

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": {
      "key": "<key>"
    },
    "name": "activate_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesIgnored. Kept so an older call still gets this answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / key / description
      Added value: +"Ignored.  Kept so an older call still gets this answer."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is fully consistent with that: it saves nothing, reads nothing it is sent, and returns sign-in steps. It adds genuinely useful behavioral context beyond the annotations by explaining why the argument is ignored and what the caller should surface to the user.

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?

The core message (retired, use kiln_signin, show the error) is front-loaded and clear. The trailing Args section restates the schema's own parameter description, which is mild redundancy, and the caveat about noving/reading nothing is stated twice, but nothing is genuinely wasted.

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

Completeness5/5

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

For a retired stub tool with one parameter and no output schema, the description covers everything: what it does, what it ignores, what it returns, and the migration path. No ambiguity remains for an agent encountering it.

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 schema already documents the single parameter. The description reinforces that ``key`` is ignored and kept only for backward compatibility, which is the key semantic point an agent needs — a small but real addition over the schema.

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?

The description states a specific, unambiguous behavior: this tool is retired, saves nothing, reads nothing, and returns sign-in instructions. It also names the replacement path (kiln_signin), so an agent can tell immediately it is not a real license-activation tool.

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

Usage Guidelines5/5

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

It explicitly covers when this tool is hit (an agent or old script still calling it), what to do with the result (show the user ``error`` verbatim, then call ``kiln_signin``), and what not to rely on (license keys stopped working 2026-11-01). The alternative is named outright.

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