Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

assess_fair_reaccomplishment

Read-only

Detect FAI re-accomplishment signals from evidence drift and assess one configuration evidence case or sweep all active cases to identify when re-approval may be needed.

Instructions

Detect FAI re-accomplishment signals from evidence drift.

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

Input Schema

NameRequiredDescriptionDefault
evidence_case_idNoThe configuration evidence case to assess. Empty (the default) sweeps every active case. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / evidence_case_id / description
      Previous value: -"Default: \"\"."New value: +"The configuration evidence case to assess. Empty (the default) sweeps every active case. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the enterprise-tier requirement, which is genuine behavioral context, but says nothing about cost, latency, or what the detection actually inspects.

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 fragments, purpose first and the tier gate second; nothing is redundant. The second line is a bare fragment rather than a full clause, but it still earns its place by flagging a blocking prerequisite.

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

Completeness3/5

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

For a read-only single-parameter tool this is nearly adequate, but there is no output schema and the description never indicates what the detection produces — flags, scores, per-case verdicts — leaving the agent unable to anticipate the response. The concept of 'evidence drift' is also left undefined.

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?

With a single optional parameter at 100% schema description coverage, the schema already explains that an empty evidence_case_id sweeps every active case. The description adds no additional meaning about scoping or identifier format, so the baseline 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 gives a specific verb and resource: 'Detect FAI re-accomplishment signals from evidence drift.' An agent knows this performs detection on FAI re-accomplishment driven by evidence drift. It does not differentiate itself from the closely related siblings manage_fair_characteristics, manage_fair_evidence_bundle, or prepopulate_fair_draft, and 'FAI'/'re-accomplishment' are left as unexplained domain jargon.

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?

'Needs Kiln Enterprise' states a real prerequisite for calling the tool, which is useful triggering context. However, there is no guidance on when to use this versus the other FAIR tools in the sibling list, nor any stated exclusion or precondition such as requiring existing evidence to have drifted.

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