Skip to main content
Glama

ENGICOR — wholesale used engines

Request a formal quotation

request_quote

Register a quotation request with ENGICOR on behalf of the buyer. Priced models get an estimated FOB quotation (valid 14 days) with a reference and a quotation link; models without a published price are registered for manual pricing. A human sales person confirms availability and sends the written Proforma Invoice within one business day. Nothing is payable or binding at this step. Only call this when the buyer has asked for a quotation and agreed to share their contact details with ENGICOR.

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": {
      "order_type": "<order_type>",
      "lines": "<lines>",
      "buyer": "<buyer>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoWho is calling
buyerYesThe buyer ENGICOR will send the Proforma Invoice to. Give email or phone.
linesYesEngine codes (e.g. "1NZ-FE", "HR16DE") and gearbox SKUs (e.g. "TR-HR16DE-CVT") with quantities.
notesNo
order_typeYesfirst_order = new customer, 20/30/40 engines (+ optional gearboxes), LCL. container_20ft = 90 engines or 45+45 gearboxes. container_40ft = 130 engines or 65+65.
destination_portNoe.g. Lagos (Apapa), Mombasa, Jebel Ali
purchase_preferenceNoremote = buy with photos/video; visit = Guangzhou Inspection Day; help = help me choose

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, open-world, not idempotent, non-destructive). The description goes well beyond that: it discloses the 14-day validity of the estimate, that a reference and quotation link are produced, that unpriced models go to manual pricing, that a human confirms availability and sends a Proforma Invoice within one business day, and that nothing is binding. That is exactly the kind of downstream-effect context an agent needs before triggering an outbound request to a third party.

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?

Four sentences, front-loaded with what the tool does, then outcomes, then the escalation path, then the usage gate. Every sentence carries distinct information — pricing behavior, timing, non-binding status, and the call condition — with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, nested-object, mutation-adjacent tool with no output schema, the description supplies what is missing elsewhere: what the caller gets back (reference, quotation link, estimated FOB), what happens offline (human confirmation, PI within one business day), and the safety framing (nothing payable or binding). Nothing an agent needs to invoke this correctly appears absent.

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 86% — the schema already documents order_type tiers, buyer contact requirements, line codes/quantities, and the purchase_preference enum. The description adds no parameter-level detail (no mention of destination_port, notes, or the agent object). With the schema doing the heavy lifting, the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: "Register a quotation request with ENGICOR on behalf of the buyer," then distinguishes two outcomes — an estimated FOB quotation for priced models versus manual pricing for unpriced ones. That is far more than a restatement of the name. It stops short of 5 because it never names the closest sibling (estimate_order) or otherwise explicitly contrasts with it.

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?

There is an explicit gating condition: "Only call this when the buyer has asked for a quotation and agreed to share their contact details with ENGICOR." The description also clarifies that nothing is payable or binding at this step, which tells the agent this is not a commitment action. It does not point to alternatives such as estimate_order or get_price_list for the pre-quotation case, so it is clear context without sibling routing.

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