Skip to main content
Glama

Lp add build

lp_add_build

Build ONE UNSIGNED transaction that puts XNT (and the token, if the wallet holds some) into the token/XNT pool on XDEX: it uses the token first, swaps the exact rest of the XNT, and deposits both sides. Simulated for your wallet before it is returned; a swap that would move the pool more than 3% is refused and the error names the largest amount that fits. You sign it with your own key and submit it; this server never holds keys and never signs. It earns a share of trading fees; it does not change faucet claims.

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": {
      "wallet": "<wallet>",
      "xntAmount": "<xntAmount>"
    },
    "name": "lp_add_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoToken mint address, or APEX (default).
walletYesYour X1 wallet public key. Fee payer and signer.
slippageNoFraction between 0.001 and 0.05. Default 0.01 (1%).
xntAmountYesXNT to use. Part of it may be swapped into the token.
apexAmountNoOptional: at most this much of the token from the wallet (default: what it holds). 0 means XNT only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / apexAmount / description
      Previous value: -"APEX to deposit, in whole tokens."New value: +"Optional: at most this much of the token from the wallet (default: what it holds). 0 means XNT only."
    • addedInput schema / properties / slippage
      Added value: +{
      +  "description": "Fraction between 0.001 and 0.05. Default 0.01 (1%).",
      +  "type": "number"
      +}
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "Token mint address, or APEX (default).",
      +  "type": "string"
      +}
    • changedInput schema / properties / xntAmount / description
      Previous value: -"Native XNT to deposit. It is wrapped for you inside the transaction."New value: +"XNT to use. Part of it may be swapped into the token."
    • changedInput schema / required
      Previous value: -[
      -  "wallet",
      -  "xntAmount",
      -  "apexAmount"
      -]New value: +[
      +  "wallet",
      +  "xntAmount"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: simulation before return, a hard refusal above 3% pool movement, and an error that reveals the largest workable amount. Custody and side-effect boundaries (no key handling, no faucet impact, earns fee share) are disclosed. It omits what a successful return payload looks like and any permission or rate limits.

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?

Four sentences, front-loaded on what gets built, then safety/simulation, then custody, then a final disambiguation clause. The faucet-claims sentence is borderline but earns its place by preempting a wrong inference.

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?

No annotations and no output schema, so the description must cover behavior and safety — it does, including custody model and refusal semantics. For a 5-parameter transaction builder, the remaining gap is the shape of the returned transaction and how the caller is expected to submit 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 coverage is 100%, so the baseline is 3. The description adds some meaning by explaining the sequencing (token used first, exact remainder of XNT swapped, then both sides deposited), which clarifies how xntAmount and apexAmount interact. It does not address the slippage parameter or its relationship to the 3% pool-move cap.

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?

Names a specific verb+resource ("Build ONE UNSIGNED transaction" that deposits XNT/token into the token/XNT pool on XDEX) and explicitly scopes it as a single unsigned transaction, which separates it from read-only siblings like lp_position and from the generic swap_build.

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

Usage Guidelines4/5

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

Makes the workflow context clear: the agent must sign with its own key and submit, and the server never holds keys or signs. It also rules out the false assumption that this affects faucet claims. It stops short of naming alternatives (swap_build, lp_position) or stating when-not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources