Skip to main content
Glama

Fillio · electronics overmolding

Recommended 3D printing resin

recommend_3d_printing_resin
Read-onlyIdempotent

Returns the SLA 3D printing resin best suited to a part's use, behaviour, service temperature and requirements, with its properties, the reasons for the choice, what remains to confirm and another option. 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_3d_printing_resin"
  }
}

Input Schema

NameRequiredDescriptionDefault
useNofunctional_prototype
langNoLanguage of the answer: “fr” or “en”.
behaviorNorigid_and_precise
requirementsNo
max_service_tempNoroom_temperature

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it safe, idempotent and closed-world, so the description's job is to add behavioural context — which it does: it discloses the return contents (chosen resin, properties, rationale, open questions, an alternative), and asserts determinism/parity with the website selector, telling the agent the answer is stable and auditable. It does not say whether the answer can be inconclusive or how conflicting requirements are resolved, so it stops short of full transparency.

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 front-loaded sentence that puts the returned entity first and then lists the supporting payload. It is dense but every clause carries information; the trailing clause about the wafer selector is the only part that could be trimmed or moved.

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?

No output schema exists, yet the description enumerates the response contents, which is exactly what an agent needs to decide whether to call it. Combined with read-only/idempotent annotations and fully enumerated parameters, little is missing; only the default/optional nature of the inputs and handling of conflicting requirements go unstated.

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 20% (only 'lang' is documented), so the description must carry weight; it does partly by naming use, behaviour, service temperature and requirements as the decision inputs. However, it adds no meaning about how enum values map to outcomes, how multiple 'requirements' entries combine, or what 'lang' defaults to, and the values themselves are only self-explanatory in the schema.

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?

Names a specific verb ('Returns') and a specific resource ('the SLA 3D printing resin best suited to...'), and scopes the inputs that drive the choice: use, behaviour, service temperature and requirements. The resource is unambiguous enough to separate it from the sibling recommend_overmolding_resin, and the description even previews the answer shape (properties, reasons, what remains to confirm, another option).

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for picking a resin given a part's use/behaviour/temperature. There is no explicit when-to-use, when-not-to-use, or routing toward siblings such as recommend_overmolding_resin, and no mention that all five inputs have defaults so a bare call is legal. The 'same as the selector on www.fillio.ca' line adds context but not selection guidance.

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