Skip to main content
Glama
Sign In
Wealthville : Solana DEFI Intelligence & AI Scoring

Wealthville : Solana DEFI Intelligence & AI Scoring

by amitesh-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_signals_feed

Read-onlyIdempotent

Retrieve recent Wealthville signals for liquidity pools, including ENTER/EXIT/RISK_OFF calls with narrative and confidence levels.

Instructions

Get the latest published Wealthville signals (ENTER/EXIT/RISK_OFF calls with narrative and confidence). Use for "any new LP signals?" questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_signals_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many signals (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds return content details but no behavioral traits beyond annotations. Consistent, no contradictions.

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?

Two sentences with no filler. First sentence defines function, second sentence usage context. Perfectly concise and front-loaded.

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

Completeness5/5

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

Simple tool with one parameter, no output schema. Description adequately covers purpose and return content. No gaps given the tool's complexity.

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 100% with parameter 'limit' fully described in schema (integer, min/max, description). Description adds no additional parameter meaning.

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?

Clearly states 'Get the latest published Wealthville signals' and specifies types (ENTER/EXIT/RISK_OFF) with narrative and confidence. Distinct from sibling tools which focus on pool scores, top pools, and track record.

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?

Explicitly says 'Use for "any new LP signals?" questions', providing clear context for when to use. No explicit when-not, but purpose is narrow enough.

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

Deploy Server

Other Tools