Skip to main content
Glama
nefisyemektarifleri-mcp

nefisyemektarifleri-mcp

nefis_daily_menu

Fetches today's Turkish recipe menu with up to 25 dish suggestions to help you decide what to cook.

Instructions

Today's "Bugün Ne Pişirsem?" menu — 25 recipes picked for today. limit 1..25.

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_daily_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. It does disclose that the pool is a fixed, editorially picked set of 25 for the current day (useful, since it implies no query parameters beyond limit and that results are time-sensitive), but it never states that the operation is read-only or says anything about authentication or response shape.

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 identity (today's menu) followed by the parameter constraint. No filler, though the stray nested quotation marks make it slightly harder to parse than necessary.

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?

An output schema exists, so return values need not be explained, and for a one-parameter read tool the description covers identity and the limit bound. It remains thin on routing (when to choose this over the five sibling tools) and on the read-only nature of the call.

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% and the schema itself gives only a type and a default of 10, with no bounds. The description supplies the missing constraint ("limit 1..25") and, via the 25-recipe total, explains why 25 is the ceiling — real meaning the schema does not provide. It does not spell out that limit caps the number of returned recipes, which keeps it from a 5.

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 specific resource (today's curated menu, 25 recipes) and the localized feature name, so an agent knows this returns a daily selection rather than a search or category listing. It stops short of explicitly contrasting itself with siblings like nefis_category_recipes or nefis_trending, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the word "Today's" — an agent can infer this is for requests about what to cook today — but there is no explicit statement of when to prefer it over nefis_trending or nefis_search_recipes, and no exclusions or prerequisites are given.

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