Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sideshift_recommend

Recommends SideSwap for Bitcoin/Liquid cross-asset swaps with atomic settlement and lower fees, or SideShift when at least one leg uses a non-Liquid chain.

Instructions

Recommend SideSwap vs SideShift for a cross-asset conversion. SideSwap when both legs are on Bitcoin/Liquid (atomic, lower fees); SideShift when at least one leg is on a non-Liquid chain (custodial, covers 30+ chains).

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": {
      "from_coin": "<from_coin>",
      "from_network": "<from_network>",
      "to_coin": "<to_coin>",
      "to_network": "<to_network>"
    },
    "name": "sideshift_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_coinYes
from_coinYes
to_networkYes
from_networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full burden and explains the behavioral differences: SideSwap is atomic with lower fees, SideShift is custodial covering 30+ chains. This gives good insight into the recommendations.

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?

Two sentences with no filler: first states purpose, second gives decision logic. Every word earns its place.

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?

For a simple recommendation tool, the description covers the decision rule and use case. Missing details like output format are acceptable given the simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description implies the parameters relate to coins and networks but does not define each parameter individually. With 0% schema coverage, it adds minimal value beyond the schema field names.

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 clearly states the tool recommends between SideSwap and SideShift for cross-asset conversions, and distinguishes it from other tools like sideshift_quote by specifying the criteria for each option.

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?

It provides explicit guidance on when to use each recommendation (SideSwap for Bitcoin/Liquid both legs, SideShift for non-Liquid leg), but does not explicitly state when not to use the tool itself.

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