Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

license_status_live

Read-only

Returns the live plan of the signed-in Kiln account by querying the server now; license key input is ignored because keys were retired on 2026-11-01.

Instructions

Return the live plan of the signed-in Kiln account, asked of the server now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "license_status_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
license_keyNoIgnored. License keys were retired on 2026-11-01; the plan shown is the signed-in account's. Kept so an older call still gets an answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / license_key / description
      Added value: +"Ignored.  License keys were retired on 2026-11-01; the plan shown is the signed-in account's. Kept so an older call still gets an answer."
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only and non-destructive annotations, “asked of the server now” discloses the operation’s freshness and server dependency. “Signed-in” also signals an account-session prerequisite, although signed-out, offline, and server-error behavior remain unspecified.

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?

The single sentence is front-loaded with the result, then adds account scope and freshness without filler. It is appropriately sized for a simple tool with no required arguments.

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 simple read with no required inputs, the resource, account scope, and live server behavior are sufficient to make a correct basic call, and the schema covers the legacy argument. The absence of an output schema makes the lack of response-shape detail more noticeable, while the relationship to license_status remains the main selection gap.

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?

The description adds no parameter detail, but the sole optional license_key parameter already has a complete schema description explaining that it is ignored, why it remains, and that the signed-in account determines the plan. With 100% schema coverage and no additional semantics in the prose, the baseline score is appropriate.

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?

“Return the live plan” identifies a specific verb and resource, while “signed-in Kiln account” and “asked of the server now” establish scope and freshness. It does not explicitly distinguish this tool from the siblings license_status or check_my_tier, so their precise differences remain unclear.

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 wording provides a clear usage context: obtaining a server-current plan for the signed-in account, with an account session implicitly required. It gives no explicit when-not guidance and does not say when license_status or another account or billing tool would be preferable.

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