Skip to main content
Glama
Sign In

Hundo

by finance.hundo
OverviewDiscussionsAdmin

propose_asset_convert

Propose converting one asset into another (a cashless swap, e.g. spend SOL to acquire a new coin). Records a sell of the source and a buy of the destination at one shared value, moving no cash account. When the user does not hold the destination yet, pass newDestAsset instead of destAssetId: confirming creates it. Returns a proposal id; to record it, call the confirm_proposal tool with the returned proposalId after the user approves (there is no UI button or proposal card to click in this context). Validates the user holds enough of the source. Pass the trade value in the user's base currency, or omit it to auto-derive from the source's market price. Always include a short user-supplied description.

MCP note: this tool only CREATES a pending proposal; nothing is recorded until confirm_proposal is called.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sourceAssetId": "<sourceAssetId>",
      "sourceQuantity": "<sourceQuantity>",
      "destQuantity": "<destQuantity>",
      "date": "<date>",
      "description": "<description>"
    },
    "name": "propose_asset_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD.
valueNoTrade value in MAJOR units of the user's base currency (the displayed amount, e.g. 850 for $850). This is the value of the source quantity at trade time; it becomes the destination's cost basis. Omit to auto-derive it from the source asset's latest market price.
descriptionYesShort description taken from the user's message, e.g. 'Swapped SOL for BONK'.
destAssetIdNoId of the asset being acquired (the destination), from getAssets. Must differ from the source. Omit it only when the user does not hold the destination yet, and pass newDestAsset instead.
destQuantityYesNumber of units of the destination asset received.
newDestAssetNoPass this INSTEAD of an asset id, only when getAssets shows the user does not hold the asset yet. Confirming the proposal creates the asset and records the trade together.
sourceAssetIdYesId of the asset being spent (the source of the swap).
sourceQuantityYesNumber of units of the source asset to spend.
editsProposalIdNoId of an existing pending proposal to update in place. Pass this when the user asks to modify a proposal you previously made (e.g. 'make it 5 SOL instead'). Look up current ids with listPendingProposals if you're unsure. Omit when proposing something new.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"Short user-supplied description, e.g. 'Swapped SOL for BONK'."New value: +"Short description taken from the user's message, e.g. 'Swapped SOL for BONK'."
  2. Changed4 schema fields changed
    • changedInput schema / properties / destAssetId / description
      Previous value: -"Id of the asset being acquired (the destination). Must already exist and differ from the source."New value: +"Id of the asset being acquired (the destination), from getAssets. Must differ from the source. Omit it only when the user does not hold the destination yet, and pass newDestAsset instead."
    • addedInput schema / properties / destAssetId / minLength
      Added value: +1
    • addedInput schema / properties / newDestAsset
      Added value: +{
+  "description": "Pass this INSTEAD of an asset id, only when getAssets shows the user does not hold the asset yet. Confirming the proposal creates the asset and records the trade together.",
+  "properties": {
+    "symbol": {
+      "description": "For crypto and stock: the ticker, e.g. \"SOL\" or \"AAPL\" (use the exchange suffix for a non-US listing, e.g. \"BBCA.JK\"). For commodity: \"gold\", \"silver\", \"platinum\" or \"palladium\". For every other type: a short name the user will recognize, e.g. \"Honda Civic 2021\".",
+      "maxLength": 100,
+      "minLength": 1,
+      "type": "string"
+    },
+    "type": {
+      "description": "crypto, stock (shares, ETFs and funds), commodity (gold, silver, platinum, palladium), real_estate, vehicle, bond or other.",
+      "enum": [
+        "crypto",
+        "stock",
+        "commodity",
+        "real_estate",
+        "vehicle",
+        "bond",
+        "other"
+      ],
+      "type": "string"
+    },
+    "unit": {
+      "description": "Commodity only, and then required: the unit the quantity is in - toz (troy ounce), g or kg. The price per unit must be in the same unit.",
+      "enum": [
+        "toz",
+        "g",
+        "kg"
+      ],
+      "type": "string"
+    },
+    "valuationMode": {
+      "description": "Omit it. \"auto\" (the default for crypto, stock and commodity) follows the market price. Pass \"manual\" only when the user says the asset has no market price, e.g. shares in a private company; its value is then the price paid until the user updates it.",
+      "enum": [
+        "auto",
+        "manual"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "type",
+    "symbol"
+  ],
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "sourceAssetId",
-  "sourceQuantity",
-  "destAssetId",
-  "destQuantity",
-  "date",
-  "description"
-]New value: +[
+  "sourceAssetId",
+  "sourceQuantity",
+  "destQuantity",
+  "date",
+  "description"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read, non-destructive, non-idempotent, closed-world write. The description adds the crucial behavior that nothing is recorded until confirm_proposal runs, that the call returns a proposal id, that source holdings are validated, and that an omitted value is auto-derived from market price and becomes the destination's cost basis.

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?

Front-loaded with purpose, then workflow, then parameter notes — good ordering. It loses a point for redundancy: the confirm_proposal dependency is stated twice (once inline, once in the trailing MCP note), and the density makes it a single long paragraph rather than scannable clauses.

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?

For a 9-parameter, nested-object, mutating tool with no output schema, the description still supplies the return value (a proposal id), the confirmation requirement, and the creation-on-confirm behavior for newDestAsset. An agent has everything needed to call it correctly and follow through.

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 100%, so the baseline is 3; the description earns above that by framing the destAssetId/newDestAsset fork as a workflow decision tied to what getAssets shows, and by explaining the value parameter's base-currency semantics and auto-derive fallback. It does not, however, discuss editsProposalId, which only the schema covers.

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?

States a specific verb and resource ("Propose converting one asset into another") and immediately pins down the mechanism with "a cashless swap ... moving no cash account," which is exactly what separates this from the sibling propose_asset_trade. It also says what side effects are recorded (a sell of the source, a buy of the destination at one shared value).

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 routing rules: use newDestAsset instead of destAssetId when the user doesn't hold the destination, then call confirm_proposal with the returned proposalId after approval, and the note that there is no UI card to click in this context. The schema extends this with the editsProposalId path for modifying an existing proposal, so both 'create new' and 'amend' cases are covered.

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

All Hundo toolsInspect
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