Skip to main content
Glama
assetfare

assetfare

by assetfare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

assetfare_create_session

Idempotent

Lock a legacy quote into a wallet-bound v1 execution session after authentication, setting source and destination wallets. Reserves an active session slot without signing or submitting a transaction.

Instructions

Lock one fresh legacy assetfare_quote into a wallet-bound v1 execution session. Use only after legacy wallet authentication for the original Solana-SOL-to-Base/Arbitrum-ETH workflow; for a v2 quote use assetfare_v2_session_create instead. Makes a network request and reserves the caller's one active legacy session slot, but creates no blockchain transaction and never signs or submits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quote_idYesFresh legacy v1 quote UUID returned by assetfare_quote. A v2 quote ID is invalid here.
access_tokenYesSensitive legacy v1 wallet-bound bearer token returned by assetfare_finish_wallet_auth. Use only with unversioned legacy session tools; never log or use it as a v2 session capability.
source_walletYesCaller-owned Solana public wallet address for the legacy v1 source. Public address only; never provide a seed phrase or private key.
idempotency_keyYesCaller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII key pattern.
destination_walletYesCaller-owned Base or Arbitrum EVM destination address as 0x plus 40 hex characters. Public address only; never provide a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Caller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation."New value: +"Caller-generated retry key, 8-128 characters. Reuse it only when retrying the same logical mutation; choose a new key for a new operation. Strict approval_v3 requests additionally enforce its ASCII key pattern."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the tool makes a network request, reserves the caller's single active legacy session slot, creates no blockchain transaction, and never signs or submits. This is valuable behavior context and does not contradict the readOnlyHint=false/idempotentHint=true annotations.

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?

Three sentences, each earning its place: core purpose, usage/alternative, and behavioral caveats. It is front-loaded with the most important information and contains no filler.

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 create-style tool with five required parameters and no output schema, the description still covers the essential selection, invocation, and safety context: prerequisites, alternative, slot reservation, and the no-transaction guarantee. Nothing needed to select or invoke it correctly is missing.

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 the schema already documents all five parameters in detail. The description adds contextual expectations like the quote being 'fresh' and v1, but it does not need to carry parameter-level semantics because the schema is complete.

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 leads with a specific verb and resource: 'Lock one fresh legacy assetfare_quote into a wallet-bound v1 execution session.' It clearly defines what the tool does and explicitly distinguishes it from the v2 session tool, so an agent can differentiate it from siblings.

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?

It states the precondition ('Use only after legacy wallet authentication'), the intended workflow (Solana-SOL to Base/Arbitrum-ETH), and names the alternative for v2 quotes (assetfare_v2_session_create). This gives explicit when-to-use and when-not-to-use guidance.

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