Skip to main content
Glama

GET_NEAR_SWAP_FULL_QUOTE

Obtain a full quote and a unique deposit address to initiate a NEAR intent swap. Requires recipient and refund addresses to proceed with the exchange.

Instructions

[STEP 2] Get a full quote with deposit address for a NEAR intent swap. This requires recipient and refund addresses and returns a unique deposit address where users can send their funds to initiate the swap. Use this when users are ready to proceed with the swap after checking the simple quote. NOTE: If users provide simple token names (e.g., 'ETH', 'USDC'), first use GET_NEAR_SWAP_TOKENS to discover the exact token IDs required for this API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
swapTypeNo(Optional, defaults to EXACT_INPUT) Whether to use the amount as the output or the input for the basis of the swap: EXACT_INPUT - request output amount for exact input, EXACT_OUTPUT - request output amount for exact output. The refundTo address will always receive excess tokens back even after the swap is complete.EXACT_INPUT
originAssetYesID of the origin asset (e.g. 'nep141:arb-0xaf88d065e77c8cc2239327c5edb3a432268e5831.omft.near')
destinationAssetYesID of the destination asset (e.g. 'nep141:sol-5ce3bf3a31af18be40ba30f721101b4341690186.omft.near')
amountYesAmount to swap as the base amount (can be switched to exact input/output using the dedicated flag), denoted in the smallest unit of the specified currency (e.g., wei for ETH)
recipientYesRecipient address. The format should match recipientType.
recipientTypeNo(Optional, defaults to DESTINATION_CHAIN) Type of recipient address: DESTINATION_CHAIN - assets will be transferred to chain of destinationAsset, INTENTS - assets will be transferred to account inside intentsDESTINATION_CHAIN
refundToNo(Optional) Address for user refund
refundTypeNo(Optional, defaults to ORIGIN_CHAIN) Type of refund address: ORIGIN_CHAIN - assets will be refunded to refundTo address on the origin chain, INTENTS - assets will be refunded to refundTo intents accountORIGIN_CHAIN
slippageToleranceNo(Optional, defaults to 100) Slippage tolerance for the swap. This value is in basis points (1/100th of a percent), e.g. 100 for 1% slippage.
dryNo(Optional, defaults to false) Flag indicating whether this is a dry run request. If true, the response will NOT contain the following fields: depositAddress, timeWhenInactive, deadline.
depositTypeNo(Optional, defaults to ORIGIN_CHAIN) Type of the deposit address: ORIGIN_CHAIN - deposit address on the origin chain, INTENTS - account ID inside near intents to which you should transfer assets inside intentsORIGIN_CHAIN
deadlineNo(Optional, defaults to 1 hour from now) Timestamp in ISO format, that identifies when user refund will begin if the swap isn't completed by then. It needs to exceed the time required for the deposit tx to be minted, e.g. for Bitcoin it might require ~1h depending on the gas fees paid.2026-05-28T01:06:14.489Z
referralNo(Optional) Referral identifier (lower case only). It will be reflected in the on-chain data and displayed on public analytics platforms.
quoteWaitingTimeMsNo(Optional, defaults to 3000) Time in milliseconds user is willing to wait for quote from relay
Behavior3/5

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

No annotations provided, so description carries full weight. Mentions it returns a unique deposit address and requires recipient/refund addresses. Does not disclose whether the call creates a pending swap or has side effects. The dry run parameter is described in schema but not highlighted in description. Lacks depth on behavioral traits like idempotency or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the main purpose. Uses a clear step label and warns about prerequisite token discovery. Every sentence adds value with no redundancy or filler.

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 14 parameters and no output schema, the description explains the core workflow but omits details about the return structure beyond 'unique deposit address'. The agent is left to infer other output fields (e.g., estimated output, fees). Lacks completeness for a complex tool with many optional parameters.

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%, so baseline is 3. The tool description adds context about requiring recipient and refund addresses, but does not elaborate on individual parameters beyond what the schema already provides. The NOTE about token names indirectly helps with originAsset/destinationAsset but does not add new semantic value.

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?

Clearly states the tool gets a full quote with deposit address for a NEAR intent swap. The '[STEP 2]' prefix and mention of checking the simple quote distinguish it from sibling tools like GET_NEAR_SWAP_SIMPLE_QUOTE. The verb 'get' and resource 'full quote' are specific and unambiguous.

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?

States to use this when users are ready to proceed after checking the simple quote. Provides a NOTE directing to GET_NEAR_SWAP_TOKENS for resolving token names. Does not explicitly say when not to use, but the context implies the simple quote is a prerequisite, leaving no ambiguity.

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/IQAIcom/mcp-near-intents'

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