Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

answer_material_question

Read-only

Answers one specific engineering question about a selected material, covering design, failure, and post-processing details.

Instructions

Answer one specific engineering question about one material.

Needs Kiln Pro.

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": {
      "material": "<material>",
      "question": "<question>"
    },
    "name": "answer_material_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialYesOne supported material name.
questionYesOne specific material, design, failure, or post-processing question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / material / description
      Added value: +"One supported material name."
    • addedInput schema / properties / question / description
      Added value: +"One specific material, design, failure, or post-processing question."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is clear. The description adds that Kiln Pro is required and that the tool handles one specific question at a time. However, it does not state whether the material must already be supported or ingested, whether answers are citation-backed, or what limits apply to question scope.

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

Conciseness5/5

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

The description is two short sentences and front-loads the core operation. 'Needs Kiln Pro' is a useful access note with no filler. Nothing is redundant or unnecessarily verbose.

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 simple two-parameter, read-only Q&A tool with full schema coverage and no output schema, the description covers the core operation and the Kiln Pro prerequisite. It does not explain sibling routing or supported-question boundaries, but those gaps are mostly usage-guideline issues rather than missing context needed to invoke the 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 the input schema already defines both material and question. The description reinforces a single-material, single-question scope but adds no format details, examples, or constraints beyond what the schema provides. This 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.

Purpose4/5

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

The description uses a specific verb and resource: 'Answer one specific engineering question about one material.' It also scopes the operation to one material and one question. It does not explicitly distinguish itself from the sibling answer_printer_question or other material-lookup tools.

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?

The description gives no when-to-use or when-not-to-use guidance, and no alternatives are named. 'Needs Kiln Pro' is an access prerequisite, not usage guidance. An agent must infer that this tool is for material questions rather than printer questions.

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