Skip to main content
Glama

ENGICOR — wholesale used engines

Price an order (no commitment)

estimate_order
Read-onlyIdempotent

Validate an order against ENGICOR's order formats and compute the FOB total and the 30/70 payment split at published list prices. Nothing is registered. Use before request_quote.

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>"
    },
    "name": "estimate_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYesEngine codes (e.g. "1NZ-FE", "HR16DE") and gearbox SKUs (e.g. "TR-HR16DE-CVT") with quantities.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is low; the description still adds value by confirming 'Nothing is registered' and by naming the pricing basis (published list prices) and the computed outputs. It does not mention rate limits, price-list staleness, or what happens if validation fails, which keeps it below a 5.

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?

Three short sentences, front-loaded with what is computed, followed by the no-side-effect guarantee and the sequencing hint. No sentence is redundant.

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 only two fully described parameters, rich annotations, and no output schema, the definition covers nearly everything an agent needs, including a partial sketch of the return values (FOB total and payment split). A note on validation-failure behavior would close the remaining gap.

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 enum meanings for order_type and the code format examples for lines are already documented in the schema. The description only reinforces the pricing context ('published list prices') without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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 verbs and resources: validate an order against order formats and compute the FOB total and 30/70 payment split. The clause 'Nothing is registered' plus 'Use before request_quote' separates it cleanly from the quote-request sibling.

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 an explicit ordering rule ('Use before request_quote'), which tells the agent exactly when this tool belongs in a workflow. It stops short of stating when not to use it (for example, once a quote already exists), so it is clear but not fully two-sided.

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