Skip to main content
Glama
Zzero-net

Zero Network MCP Server

by Zzero-net

zero_convert

Convert between USD, Z tokens, and units for crypto payment calculations in Zero Network applications.

Instructions

Convert between USD, Z tokens, and units.

Args: amount: The amount to convert direction: One of "usd_to_z", "z_to_usd", "z_to_units", "units_to_z"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
directionNousd_to_z

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the zero_convert tool handler which performs currency/unit conversion.
    @mcp.tool()
    def zero_convert(amount: float, direction: str = "usd_to_z") -> str:
        """Convert between USD, Z tokens, and units.
    
        Args:
            amount: The amount to convert
            direction: One of "usd_to_z", "z_to_usd", "z_to_units", "units_to_z"
        """
        if direction == "usd_to_z":
            z = amount / 0.01
            units = int(z * 100)
            return f"${amount:.4f} USD = {z:.2f} Z = {units} units"
        elif direction == "z_to_usd":
            usd = amount * 0.01
            units = int(amount * 100)
            return f"{amount:.2f} Z = ${usd:.4f} USD = {units} units"
        elif direction == "z_to_units":
            units = int(amount * 100)
            usd = amount * 0.01
            return f"{amount:.2f} Z = {units} units = ${usd:.4f} USD"
        elif direction == "units_to_z":
            z = amount / 100
            usd = z * 0.01
            return f"{int(amount)} units = {z:.2f} Z = ${usd:.4f} USD"
        else:
            return f"Unknown direction '{direction}'. Use: usd_to_z, z_to_usd, z_to_units, units_to_z"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does at a basic level, without mentioning permissions, rate limits, error conditions, or what the conversion entails (e.g., real-time rates, fixed values). This leaves significant gaps for a tool performing financial conversions.

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 appropriately sized and front-loaded with the core purpose. The Args section is structured but could be more integrated. There's minimal waste, though it lacks depth that might be needed for clarity.

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

Completeness3/5

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

Given the tool's moderate complexity (currency/token conversion), no annotations, and an output schema (which handles return values), the description is minimally adequate. It covers the basic operation but lacks details on conversion logic, error handling, or integration context that would make it more complete for an agent.

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 0%, so the description must compensate. It adds value by explaining the 'direction' parameter with specific enum-like values (usd_to_z, z_to_usd, etc.), which clarifies the conversion options beyond the schema's generic string type. However, it doesn't provide details on 'amount' (e.g., decimal precision, units) or contextual info like conversion rates.

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 clearly states the tool's purpose: converting between USD, Z tokens, and units. It specifies the verb 'convert' and the resources involved. However, it doesn't explicitly differentiate from sibling tools like zero_pricing_calculator or zero_estimate_cost, which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contextual factors that would help an agent choose between this and other conversion or calculation tools in the server.

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

Install Server

Other Tools

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/Zzero-net/mcp-server'

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