armut-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSL_CERT_FILE | No | Path to a CA bundle that trusts your MITM proxy's certificate. Only needed when running in an environment behind an MITM proxy. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| armut_search_servicesA | Search Armut's service catalogue (6,759 services) by keyword. query: Turkish or ASCII, e.g. "temizlik", "nakliyat", "boyaci" — matches service names/slugs; returns slug, service_id, price-guide URL and service-page URL for each match (use the slug with the other tools). |
| armut_service_detailA | Detail of one service: name, description, pro count, average rating and review count, service_id (needed for the price guide). service_slug: e.g. "ev-temizligi" (find slugs with armut_search_services). |
| armut_list_prosA | Top professionals for a service, with name, city/district, member since, bio, rating and review count, profile URL. service_slug: e.g. "ev-temizligi"; city: optional slug like "istanbul" to filter pros to that city; limit: 1..40 (the page lists up to 40). |
| armut_service_faqC | Frequently asked questions for a service, with answers (from the service page's FAQ schema). service_slug: e.g. "ev-temizligi". |
| armut_price_guideA | Price guide for a service: page-listed min/max price (TRY), 12 months of average/min/max prices with quote counts, total quotes and pro count, average rating, real example jobs with winning prices, and recent customer reviews. service_slug: e.g. "ev-temizligi"; city: optional slug like "adana" for that city's guide (default: all Türkiye). |
| armut_trending_servicesB | What's popular on Armut right now: service groups (Temizlik, Tadilat, Nakliyat…), trending and popular services with pro counts, average ratings and verified review counts, and the most-searched city+service combos. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct facet of the service catalogue: keyword search, service detail, pros, FAQ, pricing, and trending. The only mild overlap is between armut_search_services and armut_trending_services, both of which surface services, but the descriptions make the discovery-vs-popularity distinction clear.
All six tools share the armut_ prefix and snake_case, with a predictable resource-oriented pattern (search_services, service_detail, list_pros, price_guide). The mix of verb-first (search, list) and noun-first (service_detail, price_guide) forms is natural and readable rather than inconsistent.
Six tools is well within the sweet spot and each one covers a distinct capability of a read-only marketplace catalogue. No tool feels redundant or padding.
The surface covers the main research journey: find a service, inspect it, see pros, read FAQs, check prices, and see trends. Minor gaps remain, such as no standalone professional-profile detail tool (armut_list_pros only returns a profile URL) and no category or city enumeration, but agents can work around these via search and optional city slugs.