Skip to main content
Glama
nefisyemektarifleri-mcp

nefisyemektarifleri-mcp

nefis_get_recipe

Fetches complete recipe details—ingredients, amounts, steps, tips, times, servings, rating, nutrition, and author—from a Nefis Yemek Tarifleri URL or slug.

Instructions

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

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": {
      "url": "<url>"
    },
    "name": "nefis_get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the response content ('full recipe detail') but says nothing about error behavior for invalid or unreachable URLs, whether the fetch is live versus cached, or whether the operation is strictly read-only. With an output schema present, return-shape explanation is legitimately omitted, but the failure/edge behavior remains unaddressed.

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?

Front-loaded with the payload description, then immediately the parameter format and an example. No filler sentences; the only mild inefficiency is the description of the resource being a comma-separated list rather than prose, which is still scannable.

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?

For a one-parameter read tool with an output schema, the definition covers purpose and input format adequately. The remaining gap is failure handling and the indirection from a search result slug to this call, which an agent must infer on its own.

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 coverage is 0% and the single parameter is undocumented in the schema, so the description must compensate — and it does, defining the url parameter as either a full nefisyemektarifleri.com URL or a bare slug/path, with a concrete worked example. That resolves the main ambiguity (absolute URL vs. identifier) that an agent would otherwise guess at.

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?

States a specific retrieval action and enumerates exactly what the returned detail contains (ingredients, amounts, steps, tips, times, servings, rating, nutrition, author), which distinguishes it from search/listing siblings that would return summaries. It stops short of naming a sibling to contrast with, so the differentiation is inferred rather than explicit.

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 only implied: the tool takes a recipe URL or slug, which suggests it is the follow-up call once a recipe has been identified via a search or category listing. There is no explicit statement of when to prefer it over the listing siblings or what precondition (an existing slug/URL) must hold.

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