Skip to main content
Glama

Ingredient Unit Converter MCP

convert_ingredient

Read-onlyIdempotent

Convert a cooking ingredient amount between cups, tablespoons, teaspoons, milliliters, fluid ounces, grams and ounces using a per-ingredient density table (e.g. 1 cup flour = 125 g).

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": {
      "ingredient": "<ingredient>",
      "amount": "<amount>",
      "unit": "<unit>"
    },
    "name": "convert_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesUnit: cups, tablespoons (tbsp), teaspoons (tsp), milliliters (ml), fluid ounces (floz), grams (g), ounces (oz)
amountYesAmount to convert from
ingredientYesIngredient name, e.g. 'all-purpose flour', 'butter', 'honey'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: conversions are density-table driven and ingredient-specific (1 cup flour = 125 g), which tells the agent results are not simple unit ratios. It does not say how ingredients missing from the density table are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb, the input domain (units), and the mechanism (density table) in that order, then closes with a clarifying example. No filler or redundant restatement of the title.

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 simple three-parameter read-only tool this is nearly sufficient, but there is no output schema and the schema contains only one 'unit' field, leaving the result format undefined — the description never says whether it returns one converted value, all equivalent units, or a table. That is the one thing an agent needs to interpret the response, and it is absent.

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 coverage is 100% — all three parameters have descriptions, including the full unit enumeration — so the baseline is 3. The description repeats the unit list rather than adding syntax or formatting guidance, and it does not clarify the ambiguous 'unit' parameter (source vs. target).

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 verb (convert) and resource (cooking ingredient amount), names the exact supported units, and explains the mechanism (per-ingredient density table) with a concrete example. It implicitly separates itself from scale_recipe and convert_bulk by being single-ingredient and density-based, but never names those siblings explicitly.

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?

The unit list and density-table phrasing imply this is for volume↔weight conversions of one ingredient at a time, which is enough to infer when to use it. However, there is no explicit statement of when to prefer it over convert_bulk or scale_recipe, and no mention of what happens with an unknown ingredient or an unsupported unit.

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.