Skip to main content
Glama
hamrah-mechanic-mcp

hamrah-mechanic-mcp

by sepehr071

Search used cars for sale

hm_search_cars
Read-onlyIdempotent

Find used and zero-km cars sold in Hamrah Mechanic showrooms by filtering on brand, model, city, price, mileage, year, body type, fuel, gearbox, and color.

Instructions

Search the used and zero-km cars Hamrah Mechanic's showrooms sell, with filters.

Returns ad cards; hm_car gives one ad in full. Filters are inclusive; total is the match count. A brand also matches its Iranian-assembled models; those cards add maker (e.g. saipa).

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
cityNo
fuelNo
pageNo24 ads per page.
sortNoOrder of results.default
brandNoBrand slug from hm_brands (one only), e.g. toyota.
colorNo
modelNoModel slug from hm_models; needs `brand`.
max_kmNoMost km driven; 0 = zero-km only.
originNoImported, ChineseAssembly or Iranian.
gearboxNo
year_maxNoNewest model year.
year_minNoOldest model year (Solar or Gregorian, as the ad shows).
price_maxNoHighest price, million Toman.
price_minNoLowest price, million Toman (1000 = 1 billion).
installmentsNoOnly cars that can be bought in installments.
showroom_onlyNoOnly showroom stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • changedInput schema / properties / max_km / description
      Previous value: -"Most kilometres driven; 0 gives zero-km cars only."New value: +"Most km driven; 0 = zero-km only."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 24 ads each."New value: +"24 ads per page."
    • changedInput schema / properties / price_max / description
      Previous value: -"Highest price in million Toman."New value: +"Highest price, million Toman."
    • changedInput schema / properties / price_min / description
      Previous value: -"Lowest price in million Toman, e.g. 1000 for 1 billion."New value: +"Lowest price, million Toman (1000 = 1 billion)."
    • changedInput schema / properties / showroom_only / description
      Previous value: -"Only the showrooms' own stock (delivered at any branch)."New value: +"Only showroom stock."
    • changedInput schema / properties / year_min / description
      Previous value: -"Oldest model year (Solar 1395 or Gregorian 2016, as the ad shows)."New value: +"Oldest model year (Solar or Gregorian, as the ad shows)."
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context: results come back as ad cards, `total` is the match count, and Iranian-assembly matches add a `maker` field. It stops short of describing pagination or result-set limits, though the schema's page description covers 24-per-page.

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 the core action, then return shape, then the non-obvious filter and field caveat. No filler and nothing repeated from the schema.

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

Completeness3/5

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

For a 17-parameter tool with no output schema, the description adequately signals the return shape (ad cards, total count) and the one surprising field (maker). However, it omits anything about result caps, empty-result behavior, or the zero-km/used distinction's effect on filtering, leaving some gaps for a tool of this complexity.

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?

Beyond the 71%-covered schema, the description adds cross-parameter semantics the schema cannot express: filters combine inclusively (AND), and a brand filter also matches Iranian-assembled models whose cards carry an extra `maker` field. That material changes how an agent interprets results and constructs queries.

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 first sentence states a specific verb (search), resource (used and zero-km cars in Hamrah Mechanic showrooms) and scope (with filters). It also explicitly separates itself from the sibling hm_car ('hm_car gives one ad in full'), so an agent can route 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 Guidelines4/5

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

It names the alternative for detail retrieval (hm_car) and the condition that selects it, which is clear routing guidance. It doesn't state when not to use search at all, but the slug-lookup dependencies for brand/model are carried in the schema descriptions pointing at hm_brands and hm_models.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.