Skip to main content
Glama
Sign In

Formlab enclosure estimate

by io.github.formlab-dev
OverviewDiscussionsAdmin

Estimate plastic enclosure cost (Formlab)

estimate_plastic_enclosure
Read-onlyIdempotent

Ориентировочная стоимость и сроки разработки и производства пластикового корпуса для электронного прибора (промдизайн, конструкторская документация, макет, литьё в силикон, алюминиевые и стальные пресс-формы) в России. Estimate cost and lead time to design and manufacture a custom plastic enclosure for an electronic device in Russia. Данные проектного бюро Формлаб (formlab.ru): 15 реальных корпусов, тиражи от 1 до 200 000 шт.

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": {
      "length_mm": "<length_mm>"
    },
    "name": "estimate_plastic_enclosure"
  }
}

Input Schema

NameRequiredDescriptionDefault
designNocopy - копия существующего корпуса, improve - переработка внешнего вида, original - свой дизайнoriginal
quantityNoТираж, шт (1-200000)
width_mmNoШирина, мм
height_mmNoВысота, мм
length_mmYesДлина корпуса, мм (если известна только плата - размер платы + 10 мм)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely behavioral context beyond that: the estimate is grounded in 15 real enclosures from a named bureau (formlab.ru), and it names the two values returned (cost and lead time), which matters since no output schema exists. It stops short of describing estimate precision or output format.

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?

Purpose is front-loaded and easy to scan, but every sentence is delivered twice in Russian and English, which roughly doubles the length without adding information. The bilingual format is defensible given the tool's Russian scope, but it is redundancy rather than conciseness.

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 estimation tool with full schema coverage, the description supplies what is missing elsewhere: what is returned (cost and lead time), the data provenance and sample size, and the supported batch range. Only estimate accuracy and currency are left implicit.

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 five parameters are already documented, including the design enum and the 1-200,000 quantity range. The description only repeats the quantity range and adds no interpretation of the dimension fields, so baseline 3 is appropriate.

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: estimate cost and lead time for designing and manufacturing a custom plastic enclosure for an electronic device in Russia. The scope (design stages through tooling: silicone casting, aluminum and steel molds) and the dataset behind it are explicit, so the agent knows exactly what this tool produces.

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?

The description delimits the domain clearly (custom plastic enclosures for electronic devices, Russian market, batch sizes 1-200,000), which implicitly tells the agent when this tool applies. It does not state when not to use it or name alternatives, but with no sibling tools the practical risk of misrouting is low.

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

All Formlab enclosure estimate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources