nefisyemektarifleri-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| nefis_search_recipesA | Search Nefis Yemek Tarifleri recipes by dish or ingredient. query: e.g. "mercimek", "tavuk", "sütlü tatlı". limit 1..30 (13 per page — the server fetches further pages as needed). page 1..20. Returns matching recipes (title, url, serves, prep/cook times, author, saved/comment counts, video flag, image) + total results. |
| nefis_get_recipeB | Full recipe detail: ingredients with amounts, steps, tips, times, servings, rating, nutrition, author. url: a full nefisyemektarifleri.com recipe URL (e.g. https://www.nefisyemektarifleri.com/mercimek-corbasi-tarifi/) or a bare slug/path like "mercimek-corbasi-tarifi". |
| nefis_list_categoriesA | The full recipe-category tree from nefisyemektarifleri.com (top-level categories with their subcategories: name, slug, url). Use a slug from here with nefis_category_recipes. |
| nefis_category_recipesA | Recipes in one category. category: a slug from nefis_list_categories (e.g. "corba-tarifleri") or a full category URL. limit 1..30. page 1..20. sort: "popular" (default), "trending" or "newest". |
| nefis_trendingB | The most-made recipes ("En Çok Yapılanlar") — 24 recipes. limit 1..24. |
| nefis_daily_menuA | Today's "Bugün Ne Pişirsem?" menu — 25 recipes picked for today. limit 1..25. |
| nefis_healthA | Check whether nefisyemektarifleri.com is reachable right now. Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings. |
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 7 tools
Each tool targets a distinct retrieval mode: curated trending list, free-text search, single-recipe detail, category tree, recipes within a category, today's editorial menu, and a reachability probe. The only superficially similar pair (trending vs. daily menu) is clearly separated by 'most-made all-time' versus 'picked for today'. Descriptions explicitly cross-reference each other (list_categories → category_recipes), removing boundary confusion.
All names share a consistent 'nefis_' prefix and snake_case, which makes the set predictable and easy to scan. However the verb style is mixed: some are verb_noun (search_recipes, get_recipe, list_categories) while others are bare noun/adjective phrases (trending, daily_menu, health).
Seven tools is well within the ideal range and each one maps to a real browsing need (discover, search, drill down, check status). No tool feels redundant or vestigial for a recipe-site reader.
The discovery-and-read lifecycle is well covered: browse by category, search, open a full recipe with ingredients and steps, plus trending and daily menu entry points. Minor gaps exist for a read-only recipe surface — no author lookup, no 'similar/related recipes', and no way to fetch comments or ratings beyond what get_recipe inlines.