unit convert
unit_convertConvert units: length, weight, temperature, area, volume, speed, data size. value + from + to (e.g. 100 km mi, 25 c f).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| from | No | ||
| value | No |
netcafe-devkit
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden, and it does a reasonable job by spelling out the invocation contract and giving concrete examples. It does not describe output formatting or invalid-unit behavior, but for a side-effect-free conversion tool this is not a critical omission.
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 front-loaded sentence followed by an example, with no filler or redundant restating of the title. Every phrase adds either scope or usage detail.
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 three-parameter converter with no output schema, the description is reasonably complete: it communicates scope, parameter order, and examples. It could be improved by listing accepted unit aliases or edge-case behavior, but the tool is simple enough that an agent can construct a valid call.
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 coverage is 0%, so the description must compensate; it does by defining roles through the pattern 'value + from + to' and examples like '100 km mi, 25 c f'. This makes value, from, and to understandable despite the schema providing only raw types.
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 immediately states 'Convert units' and enumerates specific categories (length, weight, temperature, area, volume, speed, data size), giving a precise verb+resource scope. This also differentiates it from sibling timezone_convert by explicitly covering non-timezone unit types.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes it clear this should be used for unit conversions and shows the required input pattern 'value + from + to'. It does not explicitly mention alternatives or exclusions, but the domain is unambiguous and the sibling list reinforces that timezone conversions belong to a different tool.
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.
TDQS
A3.8/5.0
Disambiguation4/5
Most tools have clear, separate purposes: diff, redact, regex, JWT, SQL, timezone, units, QR, screenshot. The main overlap is between json_format and validate_json, since both parse and validate JSON, though their outputs differ enough to be workable.
Naming Consistency4/5
The majority follow a clear snake_case verb_noun or noun_verb pattern like diff_text, transpile_sql, and timezone_convert. sql_from_description and what_can_you_do break the pattern, but the rest is predictable and readable.
Tool Count5/5
14 tools is well-scoped for a general-purpose developer utility server. Each tool covers a distinct practical need, and the count does not feel bloated for the breadth of features offered.
Completeness4/5
The toolkit covers a broad range of everyday dev utilities: text diffing, redaction, regex, JSON/YAML, SQL, time, units, JWT, QR, and screenshots. Some common basics like base64, hashing, or URL encoding could be useful additions, but the surface is complete enough for its stated purpose.