Skip to main content
Glama

ENGICOR — wholesale used engines

Search used engines in stock

search_stock
Read-onlyIdempotent

Search ENGICOR's used-engine warehouse list (Guangzhou, ~488 engine/gearbox families, 38 makes) by engine code, vehicle model or make. Returns specs, typical vehicles, configurations held, and the wholesale list price where published (FOB Guangzhou, USD per unit). Wholesale only.

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

Input Schema

NameRequiredDescriptionDefault
makeNoOptional make filter, e.g. "Toyota"
limitNo
queryNoEngine code, vehicle or words, e.g. "2TR", "Hilux", "Corolla 1.5", "Nissan 1.6"
priced_onlyNoOnly models with a published price

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 cover the safety profile (read-only, idempotent, closed-world, non-destructive), and the description adds genuinely new behavior: what comes back (specs, typical vehicles, configurations held), currency and incoterm basis (FOB Guangzhou, USD per unit), and the caveat that price is only present 'where published'. It stops short of saying whether results are paginated or how many match in total.

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, no filler, with the resource and scope front-loaded before the return-value summary. Every clause carries information an agent would otherwise have to guess.

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 does the necessary work of enumerating the returned fields and price basis, which is the main completeness risk for a search tool. Missing only result-set behavior (pagination/limit interaction, whether an empty result is possible) for full marks.

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 coverage is 75%, so the schema already documents make, query, and priced_only with examples. The description reinforces the searchable axes and ties 'wholesale list price where published' to the priced_only flag, but adds no format or syntax detail beyond that, and never mentions the limit cap (1-50, default 10).

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?

States a specific verb ('Search') and resource ('ENGICOR's used-engine warehouse list') and quantifies the corpus (~488 families, 38 makes, Guangzhou). It also names the three lookup axes (engine code, vehicle model, make), so an agent can distinguish it from get_engine or get_price_list without opening either schema.

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?

The 'Wholesale only' line is a useful audience constraint, but there is no explicit routing guidance such as when to use this search versus get_engine for a single known code or get_price_list for pricing. The usage context is implied by the parameter set rather than stated.

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