Skip to main content
Glama

ENGICOR — wholesale used engines

Engine family detail

get_engine
Read-onlyIdempotent

Full detail of one engine family by code (e.g. "1NZ-FE", "QR25DE", "2TR-FE"): spec, typical vehicles, configurations held, list price and gearbox options if published, page and photo URLs.

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": {
      "code": "<code>"
    },
    "name": "get_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds behavior beyond that: the result includes list price and gearbox options only "if published", which warns the agent that fields may be absent and prevents misreading a null as an error.

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?

One front-loaded sentence that leads with the action and resource before the payload list, with zero filler. The colon-separated enumeration is dense but each item is information the agent would otherwise have to discover by calling.

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 productively enumerates return fields and flags conditional ones, which is the right compensation. It stops short of stating not-found behavior or whether the code must match exactly, the only meaningful omissions for a one-parameter read tool.

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 0% and the single required parameter "code" has no schema description, so the description must carry it. It partially does by giving three concrete example codes ("1NZ-FE", "QR25DE", "2TR-FE"), conveying the expected format, but says nothing about case sensitivity, exact-match vs fuzzy matching, or what happens on an unknown code.

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?

States a specific verb-and-resource pair ("Full detail of one engine family") plus the lookup key ("by code"), and enumerates the returned content (spec, vehicles, configurations, price, gearbox, URLs). It does not name or contrast with any sibling, so an agent must infer the boundary against tools like get_price_list or search_stock itself.

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 only implied: it is a lookup requiring a known engine code. There is no explicit when-to-use or when-not, and no routing to get_price_list for pricing alone or to a search tool when the code is unknown — a real gap given the price data overlaps with get_price_list.

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