Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

manage_fair_registry

Record and retrieve attested part, organization, and unit serial identities consumed by FAIR drafts to support verified design and production workflows.

Instructions

Record and read the attested identities FAIR drafts consume.

Needs Kiln Enterprise.

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": {
      "action": "<action>"
    },
    "name": "manage_fair_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoWhat the record is about, as listed per action above (design id, ``"default"``, or the unit's serial number). Required for the record actions and ``get``; unused by ``list``. Default: "".
kindNo``get`` and ``list`` only: which registry to read, ``part_identity``, ``org_profile`` or ``unit_serial``. The record actions set it themselves and ignore this. Default: "".
actionYesOne of ``record_part_identity``, ``record_org_profile``, ``record_unit_serial``, ``get`` or ``list`` (case-insensitive); anything else is refused with ``INVALID_ACTION``.
payloadNoRecord actions only: the attested values, with the keys listed per action above. Missing required keys are refused.
attested_byNoRecord actions only, required: the name of the person attesting. Default: "".
attested_onNoRecord actions only, required: the attestation date as an ISO date (``YYYY-MM-DD``), not in the future. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.5.1
    • addedInput schema / properties / action / description
      Added value: +"One of ``record_part_identity``, ``record_org_profile``, ``record_unit_serial``, ``get`` or ``list`` (case-insensitive); anything else is refused with ``INVALID_ACTION``."
    • changedInput schema / properties / attested_by / description
      Previous value: -"Default: \"\"."New value: +"Record actions only, required: the name of the person attesting. Default: \"\"."
    • changedInput schema / properties / attested_on / description
      Previous value: -"Default: \"\"."New value: +"Record actions only, required: the attestation date as an ISO date (``YYYY-MM-DD``), not in the future. Default: \"\"."
    • changedInput schema / properties / key / description
      Previous value: -"Default: \"\"."New value: +"What the record is about, as listed per action above (design id, ``\"default\"``, or the unit's serial number). Required for the record actions and ``get``; unused by ``list``. Default: \"\"."
    • changedInput schema / properties / kind / description
      Previous value: -"Default: \"\"."New value: +"``get`` and ``list`` only: which registry to read, ``part_identity``, ``org_profile`` or ``unit_serial``. The record actions set it themselves and ignore this. Default: \"\"."
    • addedInput schema / properties / payload / description
      Added value: +"Record actions only: the attested values, with the keys listed per action above. Missing required keys are refused."
  2. Addedv1.5.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds a real behavioural fact the annotations lack — the Kiln Enterprise entitlement requirement — but says nothing about attestation obligations, immutability of recorded identities, or whether records can be overwritten.

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 sentences with no filler, and the core purpose is front-loaded ahead of the entitlement note. It is efficiently written rather than padded, though the terseness leaves obvious gaps that conciseness alone cannot excuse.

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

Completeness2/5

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

This is a six-parameter tool with a nested free-form payload, five action modes, required attestation fields, and no output schema. Against that complexity, a two-sentence description covering neither the action set nor the payload shape nor return behaviour is materially incomplete, especially for the record actions that mutate a registry.

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 the schema already documents every parameter including the action enumeration, the per-action key semantics, and the payload requirement. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair and resource ("record and read the attested identities") and ties it to FAIR drafts, which is more than a restatement of the name. However, it never explains what a "FAIR registry" holds or how it differs from sibling tools like manage_fair_characteristics, manage_fair_evidence_bundle, or prepopulate_fair_draft, so the agent cannot cleanly discriminate it from neighbours.

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

Usage Guidelines2/5

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

"Needs Kiln Enterprise" is a useful prerequisite, but there is no when-to-use guidance, no exclusions, and no pointer to the sibling FAIR tools an agent should pick instead. The five action modes are only discoverable by opening the schema.

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