Skip to main content
Glama

Server Details

Aarna - 34 tools for swap quotes, liquidity pools, and trading data

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
junct-bot/aarna-mcp
GitHub Stars
0

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 DescriptionsB

Average 3.5/5 across 20 of 20 tools scored. Lowest: 2.9/5.

Server CoherenceA
Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific vault operations or data queries. Transaction-building tools (e.g., build_deposit_tx, build_withdraw_tx) handle different actions, while get_* tools retrieve specific metrics or statuses without overlap. The descriptions reinforce unique functions, eliminating confusion.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern throughout. All transaction tools use 'build_*_tx', and all query tools use 'get_*' or 'list_*', with clear, descriptive nouns (e.g., deposit_status, historical_nav). This uniformity makes the set predictable and easy to navigate.

Tool Count4/5

With 20 tools, the count is slightly high but reasonable for the comprehensive vault management domain. It covers transaction building, status checks, and data retrieval across multiple aspects (e.g., TVL, NAV, APY, user investments), though it might feel dense for simpler use cases.

Completeness5/5

The toolset provides complete coverage for vault operations, including CRUD-like actions (deposit, withdraw, stake/unstake) with queuing mechanisms, status checks for each action, and extensive data queries (historical, current metrics, user portfolios). No obvious gaps exist for the stated domain of ATV vault management.

Discussions

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

Try in Browser

Your Connectors

Sign in to create a connector for this server.