Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

preview_overage_charge

Read-only

Calculates the extra-printer charges your plan would incur for a given number of active printers, so you can preview overage costs before adding more.

Instructions

What a number of printers would cost in extra-printer charges on your plan. Free on every plan.

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": {
      "active_printer_count": "<active_printer_count>"
    },
    "name": "preview_overage_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
active_printer_countYesHow many printers to price. Must be 0 or more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / active_printer_count / description
      Added value: +"How many printers to price.  Must be 0 or more."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/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 one genuinely useful behavioral fact: the charge is 'Free on every plan,' which implies the returned amount is always zero. That claim is confusing though, because it undercuts why an overage preview would exist, and the description does not say what the response contains (amount, currency, plan name).

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 no padding, though the second sentence ('Free on every plan') is an assertion whose relation to the first is left implicit and could have been phrased to clarify that the previewed charge is always zero.

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-parameter, read-only cost preview with no output schema, the description is roughly adequate but omits what the caller receives (a currency amount? a boolean?) and how 'free on every plan' interacts with the computed charge. A single clause on the return value would close the gap.

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%, with the integer parameter documented as 'How many printers to price. Must be 0 or more.' The description's 'a number of printers' merely restates this, adding no unit, boundary, or interpretation beyond the schema. Baseline 3 is appropriate.

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 states a specific computation: the extra-printer charge a given number of printers would incur on the current plan. That is more specific than the name alone, which only says 'preview overage.' It does not distinguish itself from other cost-estimation siblings such as estimate_cost or estimate_price, and the phrase 'What a number of printers would cost' is slightly informal, but the resource (extra-printer overage) is identifiable.

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?

There is no when-to-use guidance, no prerequisite (e.g., must be authenticated to a plan), and no pointer to alternatives or the action to take if the preview shows a charge. The agent must infer that this is a pre-purchase check.

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