Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

read_material_datasheet

Read-only

Fetch material datasheet extraction rules and field catalog, and fingerprint supplied datasheet text to support structured parsing. Requires Kiln Business.

Instructions

Get the extraction rules + field catalog (and fingerprint your text).

Needs Kiln Business.

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

Input Schema

NameRequiredDescriptionDefault
textNoDatasheet text. Omit to get just the rules + field list. Default: "".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / text / description
      Previous value: -"Default: \"\"."New value: +"Datasheet text. Omit to get just the rules + field list. Default: \"\"."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description's real contribution is the tier prerequisite ('Needs Kiln Business') and the hint that supplying text triggers a fingerprint, but it never says whether that fingerprint is stored, returned, or merely computed, leaving an unstated side effect for a read-only tool.

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 the primary purpose front-loaded and the prerequisite separated out; nothing is padded. The parenthetical mid-sentence phrasing is slightly awkward and undercuts clarity, but overall it is tight.

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 one-optional-parameter, read-only tool with no output schema, the description is roughly adequate, but 'fingerprint your text' and 'field catalog' are never grounded, so an agent cannot predict what it gets back or what happens to the text it passes in.

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 coverage is 100% and the schema already explains 'Omit to get just the rules + field list. Default: ""', so the parameter is fully documented structurally. The description adds only the vague notion of fingerprinting the supplied text, which does not clarify format, size limits, or what the fingerprint affects.

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 verb ('Get') and resources ('extraction rules + field catalog'), so the rough intent is visible, but 'fingerprint your text' is undefined jargon and the phrasing (including the parenthetical) reads like an internal shorthand note rather than a statement of what the tool returns. It does nothing to distinguish itself from nearby siblings such as ingest_material_datasheet or list_ingested_materials.

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 Business' is a genuine gating condition that tells the agent when this tool is callable, and the parenthetical implies a text-present vs text-absent mode. However, there is no explicit when-to-use/when-not guidance and no pointer to the sibling that ingests a datasheet rather than returning rules.

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