Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

kiln_spend_caps_confirm_change

Confirm a pending spend cap change with the challenge ID and the person's six-digit authenticator code, completing step 2 of 2 and returning the new caps.

Instructions

Confirm a cap change with the person's six-digit code (step 2 of 2).

        Args:
            challenge_id: From ``kiln_spend_caps_request_change``.
            totp_code: The six-digit code the PERSON reads from their own
                authenticator app.  Never produce or guess it.

        Returns the new caps on success.  A refusal names its case: a
        wrong code (they may try again within the daily limit), a
        challenge that expired or was already used (ask again from step
        1), no authenticator set up on the account, or too many attempts.

Input Schema

NameRequiredDescriptionDefault
totp_codeYes
challenge_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the behavioral burden well. It discloses that a person must provide the code and the agent must never produce or guess it, and it enumerates refusal cases including wrong code, expired/used challenge, missing authenticator setup, and too many attempts.

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 description is front-loaded with the action and step context, then provides compact argument guidance and failure outcomes. Every sentence adds useful information without repetition.

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 two-step confirmation tool with no annotations and an existing output schema, the description supplies the necessary invocation context: prerequisite tool, parameter sourcing, safety constraint, success behavior, and failure cases. Nothing essential for correct use is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must define the parameters, and it does: challenge_id is sourced from kiln_spend_caps_request_change, and totp_code is the six-digit code read by the person from their authenticator app. It also adds the critical constraint not to generate or guess the code.

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 verb and resource: confirm a cap change using a six-digit code, and identifies this as step 2 of 2. This distinguishes it clearly from the related request-change step and other spend-cap tools.

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 says this is step 2 of 2 and that challenge_id comes from kiln_spend_caps_request_change. It also gives routing guidance for failures, including asking again from step 1 when a challenge expired or was already used.

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