Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_bonding_curve_token_mint

Calculate instantaneous token price, minting cost, average purchase price, and reserve backing for linear and polynomial bonding curves using deterministic formulas.

Instructions

Continuous Token Bonding Curve Price & Minting Cost Model. Calculate instantaneous token price, buy/sell minting costs, and reserve pool backing for linear and polynomial bonding curves (Pump.fun, Bancor). Discipline: CRYPTO. Governing mathematical model / formula: Price P(S) = m · Sᵇ | Total Cost to Mint = ∫ P(S) dS = (m / [b + 1]) · S^(b + 1).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_purchase_cost_eth (Total Cost to Mint Tokens), final_token_price (New Token Price After Buy), average_cost_per_token (Average Purchase Price), reserve_pool_balance (Total Collateral Locked in Curve) using current_token_supply (Current Circulating Supply (S) in Tokens), tokens_to_buy (Tokens to Purchase / Mint (ΔS) in Tokens), curve_slope_m (Curve Price Slope Coefficient (m)), curve_exponent_b (Curve Exponent Power (1 = Linear, 2 = Quadratic)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Continuous Token Bonding Curve Price & Minting Cost Model' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "bonding-curve-token-mint"

    • category (string): "crypto"

    • name (string): "Continuous Token Bonding Curve Price & Minting Cost Model"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_purchase_cost_eth (Total Cost to Mint Tokens): Formatted display string (e.g. '13.75 SOL / ETH')

      • metrics.final_token_price (New Token Price After Buy): Formatted display string (e.g. '$0.60 / token')

      • metrics.average_cost_per_token (Average Purchase Price): Formatted display string (e.g. '$0.55 / token')

      • metrics.reserve_pool_balance (Total Collateral Locked in Curve): Formatted display string (e.g. '$90.00 Total Reserve')

    • execution_time_ms (number): Latency in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
curve_slope_mNoCurve Price Slope Coefficient (m). Linear price scaling factor. Default: 2e-8. Min: 1e-10. Max: 0.001.
tokens_to_buyNoTokens to Purchase / Mint (ΔS) (Tokens). Number of new tokens to mint. Default: 5000000. Min: 1000. Max: 50000000.
curve_exponent_bNoCurve Exponent Power (1 = Linear, 2 = Quadratic). 1 for linear curve, 2 for exponential steepness. Default: 1. Min: 1. Max: 3.
current_token_supplyNoCurrent Circulating Supply (S) (Tokens). Tokens minted so far along the curve. Default: 25000000. Min: 10000. Max: 1000000000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and mostly meets it: deterministic, read-only, idempotent, stateless, zero side effects, and out-of-bounds inputs return a diagnostic error rather than throwing. One gap: it advertises 'buy/sell minting costs' but the documented outputs only cover purchase-side metrics and reserve backing, so an agent cannot tell what the sell-side path looks like.

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?

Well front-loaded with the purpose and formula before usage, boundaries, safety, and returns; headers make it scannable. It loses a point for duplication — the parameter glosses in WHEN TO USE repeat the schema verbatim, and the returns section is verbose given the outputs are just four formatted strings.

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?

No output schema exists, and the description fully compensates by documenting the response envelope (status, calculator, category, name, formula, inputs echo, metrics, execution_time_ms) and the four computed metrics with example formats. Error behavior and input-bound validation are also covered, so an agent has everything needed to call and interpret it.

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 each of the four parameters already documents meaning, units, default, and min/max. The description re-enumerates the same parameters with the same parenthetical glosses, adding no format, dependency, or edge-case guidance beyond the schema. Baseline 3 applies.

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 names a specific resource (continuous token bonding curve price/minting cost) with concrete computations: instantaneous price, buy/sell minting cost, reserve pool backing, scoped to linear and polynomial curves with named real-world analogues (Pump.fun, Bancor). It states the governing formula P(S) = m · Sᵇ explicitly, which no sibling name could be confused with (e.g. omni_token_vesting_inflation or omni_arc_length).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit WHEN TO USE / WHEN NOT TO USE sections, plus a disambiguation block routing generic queries to omni_universal_query, chained jobs to omni_batch_calculate, and schema inspection to omni_describe_solver. The exclusion (no qualitative evaluation, all inputs numeric) is stated, not implied.

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