Skip to main content
Glama
sellisd

mcp-units

by sellisd
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

MCP Cooking Units Converter

MCP Cooking Units Converter is a Python package and MCP server for converting cooking measurements (volume, weight, temperature) between common units. It is designed for integration with MCP-compatible tools and VSCode extensions.

Installation

Installing via Smithery

To install Cooking Units Converter for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @sellisd/mcp-units --client claude

Manual Installation

  1. Clone the repository:

git clone git@github.com:sellisd/mcp-units.git
cd mcp-units

  1. Install:

uv pip install .  # For normal use
# OR
uv pip install -e .  # For development

Related MCP server: cook-mcp

Usage

Available Tools

The server provides the following conversion tools:

  1. Volume Conversion

    • Convert between: ml, l, cup, tbsp, tsp

    • Example: 240ml → 1 cup

  2. Weight Conversion

    • Convert between: g, kg, oz, lb

    • Example: 454g → 1 lb

  3. Temperature Conversion

    • Convert between: Celsius (C), Fahrenheit (F)

    • Example: 180°C → 356°F

Running the Server

uvx --with . python -m mcp_units.server

Using with VSCode Extensions

This MCP server can be integrated with VSCode extensions that support the Model Context Protocol. Here's how to set it up:

  1. Install an MCP-compatible VSCode extension (e.g., Roo)

  2. Configure the extension to use this server in .roo/mcp.json:

    {
  "mcpServers": {
    "units": {
      "command": "uvx",
      "args": [
        "--with",
        ".",
        "python",
        "-m",
        "mcp_units.server"
      ],
      "disabled": false
    }
  }
}

Contact

For questions, issues, or contributions, please visit the GitHub repository.

License

This project is licensed under the MIT License.

Available Tools

3 tools
convert_temperatureA

Convert between Celsius (C) and Fahrenheit (F) temperatures

ParametersJSON Schema
NameRequiredDescriptionDefault
valueYesTemperature value to convert
from_unitYesSource temperature unit (C or F)
to_unitYesTarget temperature unit (C or F)

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It accurately indicates a conversion operation but lacks details on rounding, precision, or edge cases. The simplicity of the tool mitigates the gap, but additional context would improve transparency.

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?

The description is a single, information-dense sentence that front-loads the key action and scope. Every word is necessary, with no redundancy.

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 conversion tool with three well-described params and no output schema, the description covers the essential purpose and scope. It could mention the expected behavior (e.g., reversible, precise) but is adequate for basic use.

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% (all three parameters have descriptions). The tool description adds no extra meaning beyond what the schema already provides, meeting the baseline for this dimension.

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 clearly states 'Convert between Celsius (C) and Fahrenheit (F) temperatures,' specifying the verb (convert), the resource (temperatures), and the units. It implicitly distinguishes from sibling tools (convert_volume, convert_weight) by focusing on temperature units.

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?

No explicit guidance on when to use this tool vs alternatives, nor any mention of prerequisites, limitations, or when not to use it. The sibling tools handle different units, but the description does not address any decision criteria.

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

convert_volumeA

Convert between volume units (ml, l, cup, tbsp, tsp)

ParametersJSON Schema
NameRequiredDescriptionDefault
valueYesVolume value to convert
from_unitYesSource volume unit (ml, l, cup, tbsp, tsp)
to_unitYesTarget volume unit (ml, l, cup, tbsp, tsp)

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the conversion operation but does not disclose any behavioral traits beyond that, such as precision, edge cases, or additional constraints. It is adequate but minimal.

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?

The description is a single, clear sentence that is front-loaded with the key verb and resource. Every word serves a purpose, with no wasted text.

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 conversion tool with a complete input schema and no output schema, the description sufficiently covers the purpose and units. It is slightly lacking in behavioral details but remains adequate.

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 description merely lists the unit abbreviations already present in the schema enum. It adds no new meaning or clarity beyond what the schema provides.

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 clearly states the verb 'Convert' and the resource 'volume units', listing specific supported units (ml, l, cup, tbsp, tsp). It effectively distinguishes from sibling tools for temperature and weight conversions.

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 description implies usage for volume conversions, and siblings (temperature, weight) provide contrast, but there is no explicit guidance on when to use this tool versus alternatives or any exclusion criteria.

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

convert_weightA

Convert between weight units (g, kg, oz, lb)

ParametersJSON Schema
NameRequiredDescriptionDefault
valueYesWeight value to convert
from_unitYesSource weight unit (g, kg, oz, lb)
to_unitYesTarget weight unit (g, kg, oz, lb)

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It does not mention any limitations (e.g., precision, range), side effects, or permissions needed. As a simple conversion, this is adequate but could be more informative.

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?

The description is a single sentence, very concise, and front-loads key information. It could be slightly expanded to include a mention of the output format without losing conciseness.

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 straightforward conversion tool with 3 fully described parameters and no output schema, the description is sufficient. It covers the basic purpose and supported units, omitting only minor details like return format.

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% with detailed descriptions for each parameter. The description adds no additional meaning beyond what is already in the schema. Baseline 3 is appropriate.

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 clearly states the action ('Convert'), the resource ('weight units'), and lists the supported units explicitly. It distinguishes itself from sibling tools (convert_temperature, convert_volume) by specifying weight.

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?

No explicit guidance on when to use this tool vs. alternatives. While the name and description imply it's for weight conversion, there is no mention of when not to use it or references to sibling tools.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv0.3.3
    • First observedconvert_temperature
    • First observedconvert_volume
    • First observedconvert_weight
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

Each tool handles a distinct type of unit conversion (temperature, volume, weight) with no overlap, making them easily distinguishable.

Naming Consistency5/5

All tools follow the consistent 'convert_<unit_type>' pattern, using snake_case throughout.

Tool Count4/5

Three tools is a reasonable count for a focused unit conversion server, covering common categories but not over- or under-scoped.

Completeness3/5

The server covers temperature, volume, and weight, but misses other common unit types like length, area, or pressure, leaving notable gaps for a general 'units' server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • cook-mcp

    HZZY2019
    F
    license
    A
    quality
    D
    maintenance
    MCP server that provides cooking recipe lookup, classification, and weekly meal planning based on dietary restrictions and allergies.
    5
    -

  • mcp-units

    quantumleeps
    A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides deterministic unit conversions backed by Pint, enabling exact unit conversions, compatibility checks, and parsing of quantities for LLMs.
    5
    MIT

  • recipe-mcp

    valetdotdev
    A
    license
    A
    quality
    D
    maintenance
    An MCP server for AI-powered recipe generation and transformation, enabling users to create custom recipes from natural language descriptions and modify existing ones to meet dietary and nutritional goals.
    2
    69
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sellisd/mcp-units'

If you have feedback or need assistance with the MCP directory API, please join our Discord server