FreeDailyPro Tools

converters_units_list

Read-onlyIdempotent

Unit converter: the units of each category, with ids, symbols, aliases and a US, imperial or metric tag

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

Input Schema

Name	Required	Description	Default
`category`	No	Only this category (for example volume). Leave out for every category.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-open-world operation, so the safety burden is low. The description adds useful output context beyond annotations by naming the returned fields (ids, symbols, aliases, US/imperial/metric tag), which helps an agent know what the listing contains.

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?

It is a single front-loaded sentence with no padding, and the output-field list is helpful. The colon construction and 'Unit converter:' prefix make it slightly less crisp than a direct 'Lists all units by category' phrasing.

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 read-only listing tool with no output schema, the description supplies the essential return-content summary and relies on annotations for the safety profile. The category-filter semantics are fully covered by the schema, so only the sibling distinction is notably absent.

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 single category parameter is fully documented in the schema, including the 'leave out for every category' behavior. The tool description adds no additional parameter meaning, so the baseline of 3 applies.

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?

The description states the resource precisely: it lists the units of each category along with ids, symbols, aliases and measurement-system tags. The verb is implicit ('Unit converter:' rather than 'List units'), and it never names the sibling converters_units, so an agent must infer the listing-vs-converting distinction.

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 only implied by the phrase 'the units of each category' and the optional category parameter; there is no explicit statement of when to call this versus converters_units. The agent can infer it is a discovery step before conversion, but nothing in the description confirms or excludes that.

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

All FreeDailyPro Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?