Skip to main content
Glama

Ingredient Unit Converter MCP

common_conversions

Read-onlyIdempotent

Free lookup of the most-googled cooking conversions (1 cup flour in grams, 1 tbsp butter in grams, cup to tablespoons...).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds two useful traits beyond that: the lookup is 'free' (no cost/auth implied) and the content is a curated set of popular conversions rather than an arbitrary computation. It says nothing about the return shape or size of that list.

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?

One sentence, front-loaded with the purpose and scoped immediately by 'free' and 'most-googled'. The parenthetical examples earn their place by making the content concrete, though the trailing ellipsis and mixed units make it slightly ragged.

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 zero-parameter tool with no output schema and full annotation coverage, the description covers the essentials of what is looked up. It is missing what the response looks like (a fixed table of pairs? units? formatting), which the agent must guess since no output schema exists.

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?

The tool takes zero parameters and the schema is empty, so there is no parameter meaning to add; the description correctly signals that this is a no-argument reference call. Baseline 4 applies for a zero-parameter tool.

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?

Names a specific verb+resource ('lookup of the most-googled cooking conversions') and grounds it with concrete examples (1 cup flour in grams, cup to tablespoons). It is clear what the tool returns, though it never distinguishes itself from siblings like convert_ingredient or convert_bulk, which could plausibly serve the same need.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no reference to any sibling tool. The word 'most-googled' hints that this is a static reference for popular conversions, but the agent must infer that it is the right choice over convert_ingredient for an arbitrary amount.

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.