Skip to main content
Glama

manage_supplier_document_evidence

Create and maintain controlled supplier document evidence for Kiln designs by ingesting revisions, listing history, retrieving document text, and tracking evidence cases.

Instructions

Create and maintain controlled supplier evidence (Business+).

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_supplier_document_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhich operation to run: ``ingest_revision``, ``list_history``, ``get_document_text``, ``create_case`` or ``case_status`` (case-insensitive). Anything else is refused with ``INVALID_ACTION``.
regionNo``ingest_revision`` only: the region the document applies to; part of the document's identity. Omitted, it is ``global``. Default: "global".
purposeNo``create_case`` only: a short label for what the evidence supports; it must contain letters or numbers. Omitted, it is ``conformal_coating``. Default: "conformal_coating".
languageNo``ingest_revision`` only: the document's language; part of the document's identity. Omitted, it is ``en``. Default: "en".
bom_itemsNo``create_case`` only, optional: a BOM snapshot the caller supplies, recorded as operator-attested. Used only when no ``manual_id`` BOM is bound.
design_idNo``create_case`` only, required: the Kiln design the case is about. Default: "".
manual_idNo``create_case`` only, optional: a Kiln assembly manual for this design version whose generated BOM is bound to the case. Default: "".
created_byNoOptional caller-supplied case-author label. Kiln records it as unverified rather than authenticated identity. Default: "".
issue_dateNo``ingest_revision`` only, optional: the issue date as an ISO date (``YYYY-MM-DD``); any other format is refused. Recorded as caller-asserted, not verified. Default: "".
source_urlNo``ingest_revision`` only, optional: where the document was obtained, recorded with the revision. Kiln does not fetch or watch it. Default: "".
document_idNo``list_history`` only: the document whose revisions to list. May be omitted when ``document_revision_id`` is given; if both are given they must name the same document. Default: "".
reviewed_byNoOptional caller-supplied reviewer label. Kiln records it as unverified rather than authenticated identity. Default: "".
product_formNo``ingest_revision`` only, optional: the product's form as the operator classifies it. It is part of the document's identity, so different forms are separate documents. Default: "".
product_nameNo``ingest_revision`` only, required: the product as the document names it, verified the same way as ``supplier_name``. Default: "".
document_textNo``ingest_revision`` only, required: the full text of the supplier document. Kiln stores this exact text and its digest; empty, control-character or oversized text is refused. Default: "".
document_typeNo``ingest_revision`` only, required: one of the supported types listed above. Any other value is refused with ``INVALID_DOCUMENT_TYPE``. Default: "".
supplier_nameNo``ingest_revision`` only, required: the supplier as the document names it. It must appear inside its ``identity_spans`` span, which must be verbatim in the text. Default: "".
identity_spansNo``ingest_revision`` only: a mapping from identity field (``supplier_name``, ``product_name``, ``revision_label``, optionally ``document_type`` and ``lot_identifier``) to text quoted verbatim from ``document_text``.
lot_identifierNo``ingest_revision`` only, optional: the manufacturing lot or batch this document covers (certificates of conformance, lot test reports). When given it must appear verbatim in ``document_text`` and ``identity_spans.lot_identifier`` must quote that span; it becomes part of the document's identity, so certificates for different lots coexist. Leave it empty for living documents (TDS, SDS). Default: "".
revision_labelNo``ingest_revision`` only, required: the supplier's own revision label, verified against its span. A label already stored with different content is refused unless ``review_acknowledged`` and ``correction_reason`` are given. Default: "".
source_filenameNo``ingest_revision`` only, optional: the name of the file the text came from, recorded with the revision. Default: "".
evidence_case_idNo``case_status`` only, required: the case to re-check. Default: "".
correction_reasonNo``ingest_revision`` only: why the content under an existing revision label is being corrected. Required, with ``review_acknowledged``, for that case; otherwise optional. Default: "".
design_version_idNo``create_case`` only, required: the version of ``design_id`` the documents are attached to. Default: "".
review_acknowledgedNo``ingest_revision`` only: set ``True``, together with ``correction_reason``, to store new content under a revision label that already exists. Defaults to ``False``. Default: false.
document_revision_idNo``list_history``: a revision whose document's history to list. ``get_document_text``, required: the revision whose stored text to return. Default: "".
document_revision_idsNo``create_case`` only, required: the saved revisions to attach (duplicates are dropped). Each must exist and be active in Kiln; too few or too many is refused.
supersedes_revision_idNo``ingest_revision`` only: the ``revision_id`` of the document's currently active revision. Required whenever one is active; any other id is refused. Default: "".
currentness_attestationsNoOptional dated human checks keyed by attached ``revision_id``. Each object requires ``checked_on`` and ``basis`` and may include ``reviewed_by``. These establish an operator attestation, not automatic supplier monitoring or system-verified currentness.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changedv1.5.1
    • addedInput schema / properties / action / description
      Added value: +"Which operation to run: ``ingest_revision``, ``list_history``, ``get_document_text``, ``create_case`` or ``case_status`` (case-insensitive). Anything else is refused with ``INVALID_ACTION``."
    • addedInput schema / properties / bom_items / description
      Added value: +"``create_case`` only, optional: a BOM snapshot the caller supplies, recorded as operator-attested. Used only when no ``manual_id`` BOM is bound."
    • changedInput schema / properties / correction_reason / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only: why the content under an existing revision label is being corrected. Required, with ``review_acknowledged``, for that case; otherwise optional. Default: \"\"."
    • changedInput schema / properties / created_by / description
      Previous value: -"Default: \"\"."New value: +"Optional caller-supplied case-author label. Kiln records it as unverified rather than authenticated identity. Default: \"\"."
    • addedInput schema / properties / currentness_attestations / description
      Added value: +"Optional dated human checks keyed by attached ``revision_id``. Each object requires ``checked_on`` and ``basis`` and may include ``reviewed_by``. These establish an operator attestation, not automatic supplier monitoring or system-verified currentness."
    • changedInput schema / properties / design_id / description
      Previous value: -"Default: \"\"."New value: +"``create_case`` only, required: the Kiln design the case is about. Default: \"\"."
    • changedInput schema / properties / design_version_id / description
      Previous value: -"Default: \"\"."New value: +"``create_case`` only, required: the version of ``design_id`` the documents are attached to. Default: \"\"."
    • changedInput schema / properties / document_id / description
      Previous value: -"Default: \"\"."New value: +"``list_history`` only: the document whose revisions to list. May be omitted when ``document_revision_id`` is given; if both are given they must name the same document. Default: \"\"."
    • changedInput schema / properties / document_revision_id / description
      Previous value: -"Default: \"\"."New value: +"``list_history``: a revision whose document's history to list. ``get_document_text``, required: the revision whose stored text to return. Default: \"\"."
    • addedInput schema / properties / document_revision_ids / description
      Added value: +"``create_case`` only, required: the saved revisions to attach (duplicates are dropped). Each must exist and be active in Kiln; too few or too many is refused."
    • changedInput schema / properties / document_text / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, required: the full text of the supplier document. Kiln stores this exact text and its digest; empty, control-character or oversized text is refused. Default: \"\"."
    • changedInput schema / properties / document_type / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, required: one of the supported types listed above. Any other value is refused with ``INVALID_DOCUMENT_TYPE``. Default: \"\"."
    • changedInput schema / properties / evidence_case_id / description
      Previous value: -"Default: \"\"."New value: +"``case_status`` only, required: the case to re-check. Default: \"\"."
    • addedInput schema / properties / identity_spans / description
      Added value: +"``ingest_revision`` only: a mapping from identity field (``supplier_name``, ``product_name``, ``revision_label``, optionally ``document_type`` and ``lot_identifier``) to text quoted verbatim from ``document_text``."
    • changedInput schema / properties / issue_date / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, optional: the issue date as an ISO date (``YYYY-MM-DD``); any other format is refused. Recorded as caller-asserted, not verified. Default: \"\"."
    • changedInput schema / properties / language / description
      Previous value: -"Default: \"en\"."New value: +"``ingest_revision`` only: the document's language; part of the document's identity. Omitted, it is ``en``. Default: \"en\"."
    • changedInput schema / properties / lot_identifier / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, optional: the manufacturing lot or batch this document covers (certificates of conformance, lot test reports). When given it must appear verbatim in ``document_text`` and ``identity_spans.lot_identifier`` must quote that span; it becomes part of the document's identity, so certificates for different lots coexist. Leave it empty for living documents (TDS, SDS). Default: \"\"."
    • changedInput schema / properties / manual_id / description
      Previous value: -"Default: \"\"."New value: +"``create_case`` only, optional: a Kiln assembly manual for this design version whose generated BOM is bound to the case. Default: \"\"."
    • changedInput schema / properties / product_form / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, optional: the product's form as the operator classifies it. It is part of the document's identity, so different forms are separate documents. Default: \"\"."
    • changedInput schema / properties / product_name / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, required: the product as the document names it, verified the same way as ``supplier_name``. Default: \"\"."
    • changedInput schema / properties / purpose / description
      Previous value: -"Default: \"conformal_coating\"."New value: +"``create_case`` only: a short label for what the evidence supports; it must contain letters or numbers. Omitted, it is ``conformal_coating``. Default: \"conformal_coating\"."
    • changedInput schema / properties / region / description
      Previous value: -"Default: \"global\"."New value: +"``ingest_revision`` only: the region the document applies to; part of the document's identity. Omitted, it is ``global``. Default: \"global\"."
    • changedInput schema / properties / review_acknowledged / description
      Previous value: -"Default: false."New value: +"``ingest_revision`` only: set ``True``, together with ``correction_reason``, to store new content under a revision label that already exists. Defaults to ``False``. Default: false."
    • changedInput schema / properties / reviewed_by / description
      Previous value: -"Default: \"\"."New value: +"Optional caller-supplied reviewer label. Kiln records it as unverified rather than authenticated identity. Default: \"\"."
    • changedInput schema / properties / revision_label / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, required: the supplier's own revision label, verified against its span. A label already stored with different content is refused unless ``review_acknowledged`` and ``correction_reason`` are given. Default: \"\"."
    • changedInput schema / properties / source_filename / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, optional: the name of the file the text came from, recorded with the revision. Default: \"\"."
    • changedInput schema / properties / source_url / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, optional: where the document was obtained, recorded with the revision. Kiln does not fetch or watch it. Default: \"\"."
    • changedInput schema / properties / supersedes_revision_id / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only: the ``revision_id`` of the document's currently active revision. Required whenever one is active; any other id is refused. Default: \"\"."
    • changedInput schema / properties / supplier_name / description
      Previous value: -"Default: \"\"."New value: +"``ingest_revision`` only, required: the supplier as the document names it. It must appear inside its ``identity_spans`` span, which must be verbatim in the text. Default: \"\"."
  2. Addedv1.5.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's job is to add operational context, which it barely does. It never mentions that the tool mixes writes (ingest_revision, create_case) with reads (list_history, get_document_text), that actions are refused with INVALID_ACTION, that identity fields must be verified verbatim against the text, or that corrections require review_acknowledged plus correction_reason. Only the tier requirement is new information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler, so nothing is wasteful, but it is under-specified rather than front-loaded with anything useful. Conciseness is achieved by omission of the tool's actual operation set.

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

Completeness1/5

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

A 29-parameter, five-action, mutation-capable evidence-governance tool with no output schema needs far more than a single sentence: the action vocabulary, the write/read split, the Business+ gate consequences and the correction/attestation workflow are all absent from the description. Nothing an agent needs to choose or apply this tool safely is present outside the schema.

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 per-parameter documentation of action gating, defaults, verbatim-span verification and refusal codes is already fully carried by the schema. The description contributes nothing to parameter meaning, but the baseline of 3 applies 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.

Purpose2/5

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

The description restates the tool name almost verbatim: 'create and maintain ... supplier evidence' vs 'manage_supplier_document_evidence', which is close to tautology. It never reveals that this is a five-operation tool spanning ingestion, history listing, text retrieval, case creation and case status, nor how it differs from sibling evidence tools such as manage_fair_evidence_bundle, ingest_material_datasheet or review_magnet_supplier_packet. The only real information added is the '(Business+)' tier gate.

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

Usage Guidelines1/5

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

There is no when-to-use guidance whatsoever: no indication of which of the five actions to pick, no prerequisites, no mention of the Business+ gating condition beyond the parenthetical label, and no routing to or away from the many sibling supplier/evidence/datasheet tools. An agent must read the 29-parameter schema to discover the operations exist.

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