Skip to main content
Glama
nefisyemektarifleri-mcp

nefisyemektarifleri-mcp

nefis_category_recipes

Fetches recipes from a specified Nefis Yemek Tarifleri category using a slug or URL, with page, limit, and popular, trending, or newest sorting.

Instructions

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".

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": {
      "category": "<category>"
    },
    "name": "nefis_category_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNopopular
limitNo
categoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations present, the description has to carry behavior alone; it does disclose the hard bounds (limit 1..30, page 1..20) and the default sort, which are real behavioral constraints. It says nothing about permissions, rate limits, or pagination metadata, and the boolean 'is there a next page' treatment is left entirely to the output schema.

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?

Four short lines, one per concern, with the resource statement front-loaded and parameter facts following. The telegraphic style (no verb, fragments) is efficient but slightly clipped, and the category guidance is buried mid-paragraph rather than leading.

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 read-only listing tool with an output schema that already covers return values, the description supplies the input contract, bounds, and sort semantics a caller needs. The only meaningful gap is sibling differentiation against nefis_search_recipes and nefis_trending, which a caller must infer from tool names.

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?

Schema description coverage is 0%, so the description must compensate and largely does: it defines category's accepted formats (slug from nefis_list_categories or full URL), limit's range 1..30, page's range 1..20, and sort's three values with 'popular' as default. Scale and units are spelled out; only the meaning of the default limit value of 12 and per-parameter interaction are unstated.

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?

"Recipes in one category" names the resource and the scoping dimension (category), which is specific enough to separate it from nefis_search_recipes and nefis_daily_menu. It stops short of an explicit verb (list/fetch) and never states in one clause what it is not, so it falls just below the top band.

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?

Gives concrete operating context: the category must come from nefis_list_categories or be a full category URL, and it lists the accepted sort values with the default. It does not say when a caller should prefer this over nefis_search_recipes or nefis_trending, so no explicit exclusions are offered.

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