speed_converterConvert a value between speed units. Units: m/s (Meter per second), km/h (Kilometer per hour), mph (Mile per hour), ft/s (Foot per second), kn (Knot). Calculation runs on smart-tools.xyz.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target unit id | |
| from | Yes | Source unit id | |
| value | Yes | Amount to convert | |
| locale | No | Language for source_url (en, de, es, fr, it, nl, uk) |
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 calculation runs on smart-tools.xyz, a minor detail, but does not disclose the return format or any edge-case behavior. For a simple converter, this is acceptable but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loading the purpose and listing units compactly. No fluff or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple converter with no output schema and straightforward parameters, the description covers the essential information: what it does and what units it supports. The mention of smart-tools.xyz adds little value but is not distracting. It lacks explicit output format details, but that is not critical for this type of tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all parameters, so the baseline is 3. The description adds value by expanding unit abbreviations (e.g., m/s to Meter per second), which helps the agent understand the enum values. This goes slightly beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Convert a value between speed units', which is a clear verb+resource combination. It also lists the specific units supported, distinguishing it from other converter tools in the sibling set.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The tool's purpose is self-evident from the name and description, making it clear this is for speed conversions. It doesn't explicitly mention alternatives or exclusions, but the context of sibling converter tools provides clear differentiation. The description gives enough context for when to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, but there are notable overlaps. 'hash_generator' and 'file_hash' effectively do the same thing (SHA hashing of text), and several CSV/TSV converters (csv_to_json, csv_to_sql, table_to_csv, markdown_table) have similar input handling, though outputs differ. The sheer number of converters is clear, but these near-duplicates create some ambiguity.
Names follow a generally consistent pattern: lowercase with underscores, often ending in 'converter', 'calculator', or 'generator'. A few names like 'base64', 'lorem_ipsum', and 'transliteration' deviate from the suffix pattern, but the naming style is uniform and predictable overall.
With 73 tools, this server is far over the typical well-scoped range. While the broad utility-toolkit purpose might justify a larger set, 73 is unwieldy and pushes well into 'too many' territory, making it harder for an agent to select the right tool efficiently.
The server covers a remarkably wide range of common utilities: unit conversions, calculators, text transformations, development helpers (JSON, regex, JWT, subnet), and generators. Minor gaps exist (e.g., currency converter, time zone converter), but for a general-purpose toolkit, it is largely comprehensive.