Skip to main content
Glama
nefisyemektarifleri-mcp

nefisyemektarifleri-mcp

nefis_trending

Retrieve trending Turkish recipes from Nefis Yemek Tarifleri with an adjustable limit to identify popular dishes.

Instructions

The most-made recipes ("En Çok Yapılanlar") — 24 recipes. limit 1..24.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose a real behavioral fact the structured fields omit — the result set is bounded at 24 recipes. It says nothing about ordering guarantees, whether the list is cached/static, or any auth requirement.

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?

Two short fragments, front-loaded with the core meaning and the count before the parameter note. Slightly telegraphic but nothing wasteful.

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 one-parameter read-only listing tool with an output schema present, the description covers purpose, inventory size, and the limit bound — enough for correct invocation. Missing usage routing is the only substantive gap.

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

Parameters3/5

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

Schema description coverage is 0% and the schema only shows `limit` as an integer with default 10, so the description's "limit 1..24" adds genuine constraint information the schema lacks. It still omits what happens at the boundary or whether limit truncates the fixed 24-item list but does not paginate.

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 the resource and its ranking semantics ("most-made recipes") and even supplies the Turkish label "En Çok Yapılanlar" plus the fixed corpus size of 24, so an agent knows exactly what comes back. It stops short of distinguishing itself from siblings such as nefis_category_recipes or nefis_search_recipes, 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 explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative for category browsing or keyword lookup. The use case is only inferable from the name and the word "trending".

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