Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_airfryer_cooking_program

Look up exact air fryer temperature (°C and °F), cooking duration (minutes), and crispness tips across 186 foods, or convert oven recipes.

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

Input Schema

NameRequiredDescriptionDefault
food_itemNoFood item in German or English (e.g. Pommes, Lachs, Kuchen, Brötchen, salmon, chicken wings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned values (both temperature units, duration, tips) and the corpus size, which is useful. However, it never explains the zero-required-parameter situation (what happens if food_item is omitted), miss/fallback behavior for unrecognized foods, or how the 'convert oven recipes' mode is triggered with a single food_item argument.

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?

A single dense sentence that front-loads the primary lookup capability and the returned fields. The trailing 'or convert oven recipes' clause is a bit of a loose end given the one-parameter schema, but nothing is padded or redundant.

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?

With no output schema and no annotations, the description does reasonably well by naming the returned fields and coverage. It is still incomplete for a tool where food_item is optional: an agent cannot predict the no-argument behavior or the failure mode for an unmatched food, which matters more than return-value detail here.

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 100% and the schema already gives bilingual examples (Pommes, Lachs, salmon, chicken wings). The description adds no syntax, matching, or partial-name guidance beyond that. Baseline 3 applies since the schema does the heavy lifting.

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 gives a concrete verb (look up) and specific resources (air fryer temperature in °C/°F, cooking duration in minutes, crispness tips) plus scope (186 foods). It also mentions oven-recipe conversion, but that second capability has no corresponding parameter, leaving the purpose slightly muddied. Still, an agent can tell exactly what this tool is for and that no sibling covers it.

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 domain: query it when you need air fryer settings for a food. There is no explicit when-to-use/when-not-to-use guidance, no statement about the oven-conversion path, and no mention of what to do when the food is unknown or ambiguous. Adequate but with clear gaps.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources