Skip to main content
Glama

Fillio · electronics overmolding

Recommended overmolding resin

recommend_overmolding_resin
Read-onlyIdempotent

Returns the low-pressure overmolding polyamide family best suited to a part's service temperatures, exposures, hardness and needs, with its service range, hardness, colours, what remains to confirm with Fillio and another compatible family. Same choices and same answer as the selector on www.fillio.ca.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: “fr” or “en”.
needsNo
hardnessNoany
exposuresNo
max_service_temp_cNo
min_service_temp_cNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing the shape of the answer (service range, hardness, colours, an alternate family) and, notably, that some points 'remain to confirm with Fillio' — an honest statement of uncertainty. It says nothing about how ties or empty inputs are resolved, so a 3 rather than a 4.

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?

A single dense sentence that front-loads the returned value and then appends the credibility anchor about the fillio.ca selector. Nothing is wasted, though the packed clause listing of output fields takes a second read.

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?

With six optional parameters, low schema coverage and no output schema, the description carries a lot of weight; it does explain the return contents and the main input dimensions. It omits the all-optional nature of the call and what happens when needs/exposures are empty, which an agent would need to know to call it confidently.

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 only 17% (only 'lang' is documented), so the description must compensate. It does name four of the six inputs — service temperatures, exposures, hardness, needs — which is meaningful coverage, but it gives no enum meanings, no default behaviour for the optional fields, and never mentions the language parameter.

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 ('Returns the low-pressure overmolding polyamide family') and enumerates the criteria it matches on (service temperatures, exposures, hardness, needs) plus what the answer contains. The 'overmolding polyamide' qualifier clearly separates it from recommend_3d_printing_resin and the costing/quote siblings.

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?

Makes the usage context clear: a selection aid for overmolding resin, mirroring the selector on www.fillio.ca, so an agent knows it is the recommendation entry point for overmolding. It stops short of explicit when-not-to-use guidance or naming an alternative tool to call instead.

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