Skip to main content
Glama

Fillio · electronics overmolding

Overmolding design guide

get_design_guide
Read-onlyIdempotent

Returns Fillio's design reference for low-pressure overmolding of electronics (boards, connectors, cable junctions): when the process fits, resins, values to aim for, 3D file preparation, what the portal's analysis checks. Useful when designing or reviewing a part to be overmolded.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: “fr” or “en”.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: this is a static reference document, and it names the sections it contains (process fit, resins, target values, 3D file prep, portal analysis checks). It does not disclose return format or size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and its scope, followed by the use case. The parenthetical audience scope (boards, connectors, cable junctions) and the content list both earn their place for selection decisions.

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?

With no output schema, the description compensates by listing what the reference covers, which is the key completeness signal for a documentation-fetch tool. It stops short of indicating the response format (prose, markdown, structured sections), the only remaining gap for an agent planning to consume the output.

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% and the single `lang` parameter has an enum with a description, so the schema fully carries parameter meaning. The description adds nothing about the language parameter, which is acceptable at baseline 3.

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?

States a specific verb and resource ("Returns Fillio's design reference for low-pressure overmolding of electronics") and enumerates the covered topics, so an agent knows exactly what content it gets. It does not explicitly distinguish itself from the sibling recommend_overmolding_resin, and the mention of "resins" as covered content creates mild overlap ambiguity.

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?

"Useful when designing or reviewing a part to be overmolded" gives a clear situational trigger. There are no exclusions or named alternatives, so an agent must infer when to prefer the resin-recommendation or capability siblings 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