Skip to main content
Glama

Hive Swap

by io.github.srotzin
OverviewDiscussionsAdmin

Server Details

Cross-chain token swaps for autonomous agents on Base L2 and partner rails

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
srotzin/hive-mcp-swap
GitHub Stars
0
Server Listing
hive-mcp-swap

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion with other tools. The tool's purpose is clearly stated as a read-only Paraswap price quote on Base.

Naming Consistency4/5

The single tool name 'swap_route.quote' uses a consistent resource.action pattern with snake_case and a dot delimiter. It is descriptive and internally consistent, despite the dot being an uncommon delimiter in tool names.

Tool Count2/5

The server name 'Hive Swap' suggests a broad swap-related functionality, but only one tool is provided. A single read-only quote tool is too few for the apparent scope of a swap server.

Completeness2/5

The tool provides only quote functionality with no way to execute swaps, manage tokens, or handle other lifecycle steps. Major gaps exist for any complete swapping workflow, making the server's surface severely incomplete.

Available Tools

1 tool
swap_route.quoteA
Read-only
Inspect

Get a read-only Paraswap price quote on Base. The response identifies the actual venues returned by Paraswap. No transaction construction, execution, custody, or fee collection.

ParametersJSON Schema
NameRequiredDescriptionDefault
tokenInYesInput token symbol on Base. One of: ETH, WETH, USDC, USDT.
amountInYesAmount of input token. Must be greater than 0.
tokenOutYesOutput token symbol on Base. One of: ETH, WETH, USDC, USDT.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description reinforces this while adding specific behavioral context: the response identifies actual venues returned by Paraswap, and there is no transaction construction, execution, custody, or fee collection. This adds value beyond annotations without contradicting them.

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?

The description is two sentences, front-loaded with the core purpose, and every sentence earns its place by adding meaningful constraints. It is concise without losing necessary clarity.

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?

The tool is simple with three well-documented parameters and clear read-only semantics. The description additionally mentions the response identifies venues, which partially compensates for the lack of an output schema. It is sufficiently complete for a straightforward quote tool.

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%, and each parameter is already described in the schema. The description adds little parameter-level detail beyond confirming asset symbols and the Base network, so a baseline score of 3 is appropriate.

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 gets a read-only Paraswap price quote on Base, with a specific verb and resource. It also distinguishes what the tool does not do (no transaction construction, execution, custody, or fee collection), making the purpose 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?

The description provides clear context that this is for obtaining quotes only, explicitly excluding transaction creation and fee handling. It lacks explicit alternative tool names, but the absence of siblings and the clear read-only scope give adequate usage guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updates
    • Removedhive_earn_leaderboard
    • Removedhive_earn_me
    • Removedhive_earn_register
    • Removedswap_route.execute
    • Changedswap_route.quote3 fields changed
      • removedInput schema / properties / chain
        Removed value: -{
-  "description": "Preferred chain: base (Uniswap/OKX) or solana (Jupiter). Omit to quote all.",
-  "type": "string"
-}
      • changedInput schema / properties / tokenIn / description
        Previous value: -"Input token symbol. One of: ETH, WETH, USDC, USDT, SOL."New value: +"Input token symbol on Base. One of: ETH, WETH, USDC, USDT."
      • changedInput schema / properties / tokenOut / description
        Previous value: -"Output token symbol. One of: ETH, WETH, USDC, USDT, SOL."New value: +"Output token symbol on Base. One of: ETH, WETH, USDC, USDT."
  2. 7 tool updates
    • Addedswap_route.execute
    • Addedswap_route.quote
    • Removedswap.add_liquidity
    • Removedswap.execute_swap
    • Removedswap.get_pool_stats
    • Removedswap.get_quote
    • Removedswap.list_pools
  3. 8 tool updates
    • First observedhive_earn_leaderboard
    • First observedhive_earn_me
    • First observedhive_earn_register
    • First observedswap.add_liquidity
    • First observedswap.execute_swap
    • First observedswap.get_pool_stats
    • First observedswap.get_quote
    • First observedswap.list_pools

Related MCP Connectors

Related MCP Servers

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