Skip to main content
Glama

Fillio · electronics overmolding

Filled-in wire harness quote template

send_harness_quote_template

Returns a check of a wire harness connection list (unknown references, contacts beyond the number of positions, duplicate contacts or wires, connectors with no wire or no length) and what the project still needs for a quote, and emails Fillio's Excel quote request template, filled in with the project, connectors, connections (from-to) and lengths, to the given address. The file goes to that address only; Fillio is notified (address, company, part). Useful when preparing a wire harness assembly quote request.

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": {
      "email": "<email>"
    },
    "name": "send_harness_quote_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: “fr” or “en”.
emailYesEmail address that receives the filled-in file (that of the person requesting the quote).
lengthsNoLengths: one row per branch, between its two ends (reference or junction), with the length and tolerance in millimetres.
projectNoProject: company, part, quantities, target date, who supplies the components, overmolding of a junction; every field is optional.
connectorsNoConnectors: one row per end of the harness (ref. J1, J2…), with the manufacturer, housing and contact part numbers and number of positions.
connectionsNoConnections (from-to): one row per wire, from one reference and contact to another, with the gauge, colour and wire type.

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?

The description adds substantial behavior beyond the annotations: it lists the validation checks performed, says the file is emailed only to the given address, and notes that Fillio is notified with address, company, and part. It does not explicitly warn that repeated calls send multiple emails, though the non-idempotent annotation already signals this.

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 definition is compact and front-loads the main action, but the first sentence is long and bundles validation plus emailing. It is efficient overall, with the final sentence providing a clear use case.

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 complex tool with six parameters, nested objects, and no output schema, the description covers the main action, validation categories, external email side effect, and notification behavior. Minor gaps remain around the vague phrase 'what the project still needs for a quote' and the unmentioned language parameter.

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 the nested fields are already well documented. The description maps the email, project, connectors, connections, and lengths inputs to the quote template, but it omits the language parameter and adds little field-level meaning beyond 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?

The description states specific actions and resources: it checks a wire harness connection list and emails Fillio's filled-in Excel quote request template. This is clearly distinguishable from siblings such as cost estimation, capabilities, or resin recommendation tools.

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?

It gives a clear usage context with 'Useful when preparing a wire harness assembly quote request.' However, it does not state when not to use the tool or name any alternative workflow.

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