Skip to main content
Glama

ENGICOR — wholesale used engines

Trade terms

get_terms
Read-onlyIdempotent

ENGICOR's trade terms: what is sold and how engines are checked, order formats and minimums, payment (30% / 70%, T/T), what is not covered, warranty, markets served, inspection visit, contacts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without prose. The description's only addition is disclosing the subject matter the payload covers, which helps the agent decide whether the answer is inside this document. It says nothing about currency, market/locale specificity, or whether terms are static or periodically revised.

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?

A single front-loaded sentence with no filler, leading with the owning entity and the resource before listing topics. The comma-separated inventory is dense and slightly list-like, but every item is a genuine topic an agent might query, so nothing is wasted.

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 parameterless, read-only reference fetch with no output schema and full annotation coverage, the description supplies the one thing structured data cannot: what the returned document contains. It is close to complete, with only minor gaps around return format and whether terms are market-specific.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema carries no semantics that the description must compensate for; the baseline for a no-parameter tool applies. The description is not obligated to explain inputs, and it correctly spends its words on content scope instead.

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 names a specific resource (ENGICOR's trade terms) and enumerates its scope: order formats and minimums, payment split 30/70 T/T, warranty, markets, inspection, contacts. An agent knows exactly what content this retrieves. It stops short of a verb-first formulation and never contrasts itself with siblings such as get_price_list or request_quote, so it does not earn a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites, and no routing to alternatives. The agent must infer that this is the reference lookup for commercial policy, as opposed to get_price_list for pricing or estimate_order for order math, purely from the topic 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