Skip to main content
Glama

Fillio · electronics overmolding

Real cost of in-house potting

estimate_in_house_potting_cost
Read-onlyIdempotent

Returns the real cost per working part of one year of in-house potting (epoxy or resin encapsulation), comparable with a quote: labour, engineering, rejects, returns, resin, curing space, equipment, health and safety, and delays. Same calculation as the calculator on www.fillio.ca; a missing argument takes the calculator's default value. Nothing is stored or sent.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: “fr” or “en”.
weeks_addedNoWeeks added to the project (wk)
assembly_valueNoFull value of one assembly ($)
parts_per_yearNoParts produced per year (parts)
cost_per_returnNoCost of one return ($)
cure_time_hoursNoCure time (h)
resin_wasted_pctNoWasted or expired resin (%)
equipment_per_yearNoAmortized equipment and upkeep ($/yr)
rejected_parts_pctNoRejected parts (%)
resin_cost_per_partNoResin per part ($)
delay_value_per_weekNoValue of a one-week delay ($)
parts_potted_per_dayNoParts potted per day (parts)
health_safety_per_yearNoHealth and safety, waste, training ($/yr)
operator_rate_per_hourNoLoaded hourly rate, operator ($/h)
space_cost_per_ft2_yearNoAnnual cost of space ($/ft²)
potting_minutes_per_partNoPotting time per part (min)
customer_returns_per_yearNoCustomer returns per year (returns)
engineering_rate_per_hourNoLoaded hourly rate, engineering ($/h)
engineering_hours_per_monthNoEngineering hours on potting (h/month)
floor_space_per_curing_part_ft2NoFloor space per curing part (ft²)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond them: 'Nothing is stored or sent' reinforces the side-effect-free nature, and 'a missing argument takes the calculator's default value' explains default handling for the 20 optional parameters.

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 description is compact and front-loads the return value before elaborating cost components. It could be split into two sentences for readability, but every clause contributes relevant information with no filler.

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 read-only calculator with 20 optional parameters and no output schema, the description gives the core return meaning ('real cost per working part'), the cost categories included, default behavior, and that nothing is stored. It does not describe whether the output is a single number or a breakdown, but the primary return is clear enough for correct invocation.

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 20 parameters are already documented with labels, types, defaults, and minimums. The description adds only the general note that omitted arguments use defaults, which is largely inferable from the schema's default values, and does not explain parameter interactions.

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 ('Returns') and resource ('real cost per working part of one year of in-house potting') and immediately distinguishes it as a cost-estimation tool rather than a recommendation or quote-sending tool. The list of included cost components further sharpens what it computes.

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

Usage Guidelines4/5

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

Provides clear context that the result is 'comparable with a quote' and that it mirrors a known calculator, which helps an agent decide when to call it. It does not explicitly say when not to use it or name sibling alternatives, but the use case is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources