Skip to main content
Glama

Server Details

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

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
srotzin/hive-mcp-swap
GitHub Stars
0
Server Listing
hive-mcp-swap

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.2/5 across 1 of 1 tools scored.

Server CoherenceA
Disambiguation5/5

With only a single tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as read-only quote retrieval.

Naming Consistency4/5

The single tool name 'swap_route.quote' is internally consistent, but the use of a dot as a separator is unconventional for MCP tool names. Since there is no other tool to compare, it does not exhibit inconsistency.

Tool Count3/5

A single tool feels thin for a server named 'Hive Swap', even if the scope is limited to quotes. It borders on insufficient, but given the explicit read-only nature, it might be intentionally minimal.

Completeness2/5

The server provides only quotes and explicitly omits transaction construction, execution, and custody. This leaves a significant gap for a swap-related server, as users cannot actually execute trades.

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.
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.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.