Skip to main content
Glama
Sign In

Wealthville

by io.github.amitesh-m
OverviewDiscussionsAdmin

get_pool_score

Read-onlyIdempotent

Get the Wealthville verdict (ENTER/HOLD/EXIT/AVOID) and scores (enter/hold/exit + composite Wealthville Score, 0-100) for one liquidity pool. Use before recommending or opening any LP position. Accepts a Solana pool address (base58) or an EVM 0x address / DefiLlama pool UUID.

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": {
      "pool_address": "<pool_address>"
    },
    "name": "get_pool_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_addressYesPool address: Solana base58, EVM 0x, or DefiLlama UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by specifying the output (verdict options and score range) and input flexibility (multiple address types), without contradicting annotations.

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 concise sentences. The first sentence front-loads the core function and output, and the second provides usage guidance and input requirements. No wasted words.

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 description specifies the output in detail (verdict categories and score names/range) and the input format (address types). Without an output schema, this provides sufficient context for the agent. Minor missing detail on exact JSON structure prevents a 5.

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 coverage is 100%, with the parameter description in the schema matching the tool description. The description does not add new semantic meaning beyond what the schema already provides, so baseline 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 verb 'Get' and identifies the specific data returned (Wealthville verdict and scores) for one liquidity pool. It distinguishes itself from sibling tools like get_top_pools by focusing on individual pool assessment.

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 explicitly says 'Use before recommending or opening any LP position,' providing clear context for when to invoke the tool. It does not explicitly compare to alternatives or state when not to use, but the guidance is sufficient.

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

All Wealthville toolsInspect
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