Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

estimate_timeline

Read-only

Estimate order-to-delivery timelines with per-stage breakdowns for 3D printing orders, including production, quality check, packaging, and shipping days.

Instructions

Estimate order-to-delivery timeline with per-stage breakdown.

        Args:
            technology: Manufacturing technology (FDM, SLA, SLS, MJF, DMLS).
            shipping_days: Known shipping days from a quote (optional).
            quantity: Number of copies (larger quantities add production time).
            country: Destination country code for shipping estimate fallback.

        Returns a stage-by-stage timeline (order confirmation, production,
        quality check, packaging, shipping) with estimated days per stage
        and a total delivery date.

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": {
      "technology": "<technology>"
    },
    "name": "estimate_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoDestination country code for shipping estimate fallback. Default: "US".
quantityNoNumber of copies (larger quantities add production time). Default: 1.
technologyYesManufacturing technology (FDM, SLA, SLS, MJF, DMLS).
shipping_daysNoKnown shipping days from a quote (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / country / description
      Previous value: -"Default: \"US\"."New value: +"Destination country code for shipping estimate fallback. Default: \"US\"."
    • changedInput schema / properties / quantity / description
      Previous value: -"Default: 1."New value: +"Number of copies (larger quantities add production time). Default: 1."
    • addedInput schema / properties / shipping_days / description
      Added value: +"Known shipping days from a quote (optional)."
    • addedInput schema / properties / technology / description
      Added value: +"Manufacturing technology (FDM, SLA, SLS, MJF, DMLS)."
  2. Changed5 schema fields changedv1.5.0
    • removedInput schema / properties / country / default
      Removed value: -"US"
    • addedInput schema / properties / country / description
      Added value: +"Default: \"US\"."
    • removedInput schema / properties / quantity / default
      Removed value: -1
    • addedInput schema / properties / quantity / description
      Added value: +"Default: 1."
    • removedInput schema / properties / shipping_days / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: it enumerates the five returned stages, states that a total delivery date is produced, and notes that larger quantities add production time and that country is only a fallback for shipping estimates. It does not discuss estimate accuracy or assumptions, keeping it below 5.

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?

The opening one-liner is well front-loaded, and the Returns paragraph earns its place because there is no output schema. However, the Args block duplicates schema descriptions that are already 100% covered, which is pure redundancy and dilutes the definition.

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?

With no output schema, the description correctly compensates by describing the returned stage-by-stage breakdown and total date. For a read-only estimation tool with fully documented parameters, this is close to complete; only estimation assumptions and accuracy caveats are missing.

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 all four parameters. The Args block restates those descriptions almost verbatim (technology list, quantity note, country fallback), adding essentially no new meaning. Baseline 3 is correct when the schema does the work.

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 first sentence gives a specific verb and resource: 'Estimate order-to-delivery timeline with per-stage breakdown.' That is clearly distinct from siblings like estimate_print_time, estimate_cost, or estimate_price. It stops short of naming an alternative explicitly, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is a pre-order planning tool, but the description never says when to prefer it over estimate_print_time, estimate_price, or estimate_print_progress, nor does it state prerequisites. No exclusions or alternative routing are given.

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