Skip to main content
Glama
Ingredient Convert MCP

Ingredient Convert MCP

convert_bulk

Read-onlyIdempotent

Convert many ingredient amounts at once between grams, cups, and other units, with unknown items reported individually so one bad entry does not fail the batch.

Instructions

Convert many ingredient amounts at once (grams to cups, cups to grams, etc.). Unknown ingredients are reported per item instead of failing the batch.

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": {
      "items": "<items>"
    },
    "name": "convert_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesEach entry: ingredient, amount, unit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds genuinely useful behavioral detail beyond those annotations: unknown ingredients are reported per item rather than causing the whole batch to fail.

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?

Two tightly written sentences with the primary action front-loaded and the partial-failure behavior immediately following. Every sentence carries useful information, and there is no redundant wording.

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 simple read-only batch tool, annotations cover safety and the schema fully documents the single items parameter. The description covers purpose and partial-failure behavior, though it does not explicitly describe the shape of successful results, which matters slightly more because there is no output schema.

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 items array and its nested fields are already fully documented in the schema. The description reinforces the bulk nature and gives unit examples, but adds no syntactic or structural meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Convert many ingredient amounts at once' and gives concrete examples like grams to cups. The word 'bulk' in the tool name plus 'many ... at once' clearly separates it from single-item conversion siblings such as convert_ingredient.

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 bulk framing implies that this tool is for multiple items, but the description never explicitly says when to use it instead of convert_ingredient or other siblings. It also gives no exclusions or prerequisites, leaving routing guidance mostly inferred.

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