Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Unit Convert

unit_convert
Read-only

Converts numeric values between common length, weight, volume, and temperature units, enabling quick measurement translations for calculations and documentation.

Instructions

Convert numbers between common units (length: km/mi/m/ft/cm/in, weight: kg/lb, volume: l/gal, temperature: c/f/k).

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": {
      "value": "<value>",
      "from_unit": "<from_unit>",
      "to_unit": "<to_unit>"
    },
    "name": "unit_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
to_unitYes
from_unitYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe, side-effect-free operation. The description adds the supported-unit envelope, which implicitly tells the agent what will fail, but says nothing about how unsupported or mismatched units are handled (error vs. silent fallback), case sensitivity of unit strings, or rounding/precision of results.

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 dense sentence that front-loads the action and places the supported-unit inventory in a compact parenthetical. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-format explanation is unnecessary, and the three simple scalar parameters are fully scoped by the unit lists. For a low-complexity three-parameter conversion tool with readOnlyHint, nothing essential for a correct call is missing.

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?

Schema description coverage is 0% and there are no enums, so the schema alone gives no guidance on accepted values. The description compensates well by listing the valid unit tokens per dimension (length, weight, volume, temperature), effectively documenting the from_unit/to_unit domains. It falls short of mapping these lists to the specific parameter names or specifying case/format conventions.

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?

States a specific verb (convert) and resource (numbers between units) and enumerates the exact unit families supported, so an agent knows precisely what this does and its boundaries. The scope is narrow enough to distinguish it from a general calculator sibling even without naming 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 enumerated unit families — any conversion among km/mi/m/ft/cm/in, kg/lb, l/gal, c/f/k clearly belongs here. However, there is no explicit when-to-use or when-not guidance, and no routing to the 'calculate' sibling for arithmetic outside these units.

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

Deploy Server

Other Tools