Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_fulfillment_quote_cached

Read-only

Retrieve the newest cached fulfillment quote for a design file to reuse a recent price without a second provider call. Expired quotes are skipped; fetch a fresh quote instead.

Instructions

Read back the newest quote fulfillment_quote cached for a file.

Quotes are kept for a while after they are fetched, so a decision made
a few minutes later needs no second provider call.  An expired quote is
not returned; fetch a fresh one with ``fulfillment_quote``.

Args:
    file_path: Path to the design file the quote was fetched for.
    provider: Provider name as it appears in a ``fulfillment_quote``
        result (e.g. ``"craftcloud"``), used to find the cached quote.
    material: Material id the quote was fetched for (from
        ``fulfillment_materials``).

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": {
      "file_path": "<file_path>"
    },
    "name": "get_fulfillment_quote_cached"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoMaterial id the quote was fetched for (from ``fulfillment_materials``).
providerNoProvider name as it appears in a ``fulfillment_quote`` result (e.g. ``"craftcloud"``), used to find the cached quote.
file_pathYesPath to the design file the quote was fetched for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / file_path / description
      Added value: +"Path to the design file the quote was fetched for."
    • addedInput schema / properties / material / description
      Added value: +"Material id the quote was fetched for (from ``fulfillment_materials``)."
    • addedInput schema / properties / provider / description
      Added value: +"Provider name as it appears in a ``fulfillment_quote`` result (e.g. ``\"craftcloud\"``), used to find the cached quote."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / material / default
      Removed value: -null
    • removedInput schema / properties / provider / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A4.3/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 the safety profile is covered. The description adds real behavioral context beyond that: quotes persist for a while, expired entries are withheld, and no provider call is incurred. It stops short of saying what happens when nothing is cached (error vs. empty result), which matters for a read tool with no output schema.

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?

The opening sentence is front-loaded with purpose and the second paragraph carries the caching rationale and the escape hatch, with zero filler. The Args section, however, duplicates schema text already visible to the agent, so a chunk of the description does not earn its place.

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 read-only, three-parameter tool with full schema coverage, the description covers purpose, cache lifetime, expiry behavior, and the fallback tool. The remaining gap is the not-found/expired return behavior, which the agent must know since there is no output 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 all three parameters are already documented, including the 'craftcloud' provider example. The Args block restates those descriptions almost verbatim rather than adding syntax, defaults, or matching rules (e.g. whether provider/material are optional filters that widen or narrow the lookup). Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource with scope: 'Read back the newest quote cached for a file.' The word 'cached' plus 'newest' distinguishes it from the live-fetch sibling fulfillment_quote, which is named explicitly. An agent can select this tool without opening either schema.

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

Usage Guidelines5/5

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

Gives the positive condition ('a decision made a few minutes later needs no second provider call') and the negative/exclusion ('An expired quote is not returned; fetch a fresh one with fulfillment_quote'). The alternative tool and the condition that selects it are both spelled out.

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