Skip to main content
Glama

get_etf_price_by_paloma_denom

Retrieve ETF price data using Paloma denomination identifiers for cross-chain trading operations on Paloma DEX.

Instructions

Get ETF price by Paloma denomination.

Args:
    paloma_denom: Paloma denomination (e.g., factory/paloma18xrvj2ffxygkmtqwf3tr6fjqk3w0dgg7m6ucwx/palomagold)

Returns:
    JSON string with ETF price data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paloma_denomYes

Implementation Reference

  • The main handler function for the 'get_etf_price_by_paloma_denom' tool. It fetches ETF price data from the PalomaDEX API using the provided Paloma denomination by making an HTTP GET request and returns formatted JSON with the pricing information or error details.
    async def get_etf_price_by_paloma_denom(ctx: Context, paloma_denom: str) -> str:
        """Get ETF price by Paloma denomination.
        
        Args:
            paloma_denom: Paloma denomination (e.g., factory/paloma18xrvj2ffxygkmtqwf3tr6fjqk3w0dgg7m6ucwx/palomagold)
        
        Returns:
            JSON string with ETF price data.
        """
        try:
            paloma_ctx = ctx.request_context.lifespan_context
            
            # Call Paloma DEX API to get custom pricing by denom
            # Note: This endpoint might need to be confirmed with Paloma team
            api_url = f"https://api.palomadex.com/etfapi/v1/customprice?paloma_denom={paloma_denom}"
            
            response = await paloma_ctx.http_client.get(api_url)
            if response.status_code == 200:
                price_data = response.json()
                
                result = {
                    "paloma_denom": paloma_denom,
                    "pricing": price_data,
                    "timestamp": asyncio.get_event_loop().time(),
                    "source": "paloma_dex_api_denom"
                }
                
                return json.dumps(result, indent=2)
            else:
                return f"Error: Failed to fetch ETF price for denom {paloma_denom}. Status: {response.status_code}"
                    
        except Exception as e:
            logger.error(f"Error getting ETF price by paloma denom: {e}")
            return f"Error getting ETF price by paloma denom: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns 'JSON string with ETF price data,' which adds some value beyond the basic purpose. However, it lacks critical details such as whether this is a read-only operation, potential error conditions, rate limits, or authentication requirements. For a tool with zero annotation coverage, this is insufficient.

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 appropriately sized and front-loaded, with the purpose stated first, followed by clear sections for 'Args' and 'Returns.' Each sentence earns its place by providing essential information without redundancy. The structure is efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (1 parameter, no output schema, no annotations), the description is partially complete. It covers the purpose and parameter semantics well but lacks usage guidelines and behavioral details like error handling or data format specifics. Without an output schema, the return value description ('JSON string with ETF price data') is vague, leaving gaps in understanding the tool's full context.

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

Parameters4/5

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

The description adds significant meaning beyond the input schema, which has 0% description coverage. It explains that 'paloma_denom' is a 'Paloma denomination' and provides an example ('factory/paloma18xrvj2ffxygkmtqwf3tr6fjqk3w0dgg7m6ucwx/palomagold'), clarifying the parameter's format and usage. This compensates well for the schema's lack of documentation, though it doesn't detail all possible values or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get ETF price by Paloma denomination.' It specifies the verb ('Get') and resource ('ETF price'), and distinguishes it from sibling tools like 'get_etf_price' and 'get_etf_price_by_symbol' by focusing on Paloma denomination. However, it doesn't explicitly contrast with these siblings in the description text, so it's not a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_etf_price' or 'get_etf_price_by_symbol', nor does it specify scenarios where Paloma denomination is required over other identifiers. Without this context, users must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VolumeFi/mcpPADEX'

If you have feedback or need assistance with the MCP directory API, please join our Discord server