Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

require_recent_auth

Read-only

Verify that the caller signed in within a configurable recent window before allowing sensitive actions. Set provider, account, and max age; requires Kiln Enterprise.

Instructions

Step-up check: did the person behind this call sign in recently?

Needs Kiln Enterprise.

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": "require_recent_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoOn a local install, the linked sign-in identity whose last sign-in is timed, for example ``"github"`` (the default). Kiln's servers time the request's own sign-in instead. Default: "github".
tenant_idNoOn a local install, the account to check; omitted, this install's license is used. On Kiln's servers, omit it or pass your own account: any other is refused.
max_age_minutesNoHow recent the sign-in must be, in minutes. Defaults to ``15``; a value below 1 is refused. Default: 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / max_age_minutes / description
      Previous value: -"Default: 15."New value: +"How recent the sign-in must be, in minutes. Defaults to ``15``; a value below 1 is refused. Default: 15."
    • changedInput schema / properties / provider / description
      Previous value: -"Default: \"github\"."New value: +"On a local install, the linked sign-in identity whose last sign-in is timed, for example ``\"github\"`` (the default).  Kiln's servers time the request's own sign-in instead. Default: \"github\"."
    • addedInput schema / properties / tenant_id / description
      Added value: +"On a local install, the account to check; omitted, this install's license is used.  On Kiln's servers, omit it or pass your own account: any other is refused."
  2. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a real prerequisite — Enterprise tier is required — which is useful gating context, but it says nothing about what a failed check returns or how a refusal surfaces to the agent.

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?

Two short lines with the core question front-loaded and the Enterprise prerequisite immediately after. Nothing is wasted, though the interrogative phrasing is slightly oblique compared with a direct verb+resource statement.

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 zero-required-parameter read-only check with 100% schema coverage and no output schema, the description covers purpose and the tier prerequisite. The one residual gap is that it does not say what the result communicates (fresh vs stale, or an auth-required error), which matters for a decision tool.

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?

Schema description coverage is 100%, so all three parameters (provider, tenant_id, max_age_minutes) are fully documented in the schema, including defaults and the tenant-refusal rule. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 check — whether the caller signed in recently — and frames it as a 'step-up check', which conveys both the operation and its role in an auth flow. It is clearly distinguishable from siblings like kiln_signin or check_my_tier by name and intent, though it never states that differentiation explicitly.

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

Usage Guidelines3/5

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

'Step-up check' implies it is used before a privileged action to verify sign-in freshness, but no explicit when-to-use, when-not-to-use, or alternative (e.g. check_my_tier, get_session_log) is named. The gating condition 'Needs Kiln Enterprise' is the only stated context.

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