Get the latest published Wealthville signals (ENTER/EXIT/RISK_OFF calls with narrative and confidence). Use for "any new LP signals?" questions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many signals (default 20) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds narrative and confidence details beyond annotations, which already declare readOnly, openWorld, idempotent hints. No contradictions; useful context for the agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with action, no filler. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is simple with one parameter and no output schema; description covers purpose, usage, and parameter context completely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and describes the 'limit' parameter well. Description does not add extra meaning beyond the schema, baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states verb 'Get', resource 'latest published Wealthville signals', and specifies signal types (ENTER/EXIT/RISK_OFF). Distinct from siblings like get_pool_score and get_track_record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states use case: 'Use for "any new LP signals?" questions.' Lacks guidance on when not to use or alternatives, but clear context is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: scoring a specific pool, retrieving signal feed, ranking top pools, and showing track record. No overlap exists between the tool functionalities.
All tool names follow the consistent 'get_' prefix followed by a noun phrase (pool_score, signals_feed, top_pools, track_record), maintaining a predictable verb_noun pattern.
With 4 tools, the set is well-scoped for a focused server providing liquidity pool scoring, signals, rankings, and performance history. No unnecessary tools and no missing essential ones for the core domain.
The tools cover the key operations: individual pool score, latest signals, top pools ranking, and track record. Minor gaps like historical pool scores or filtering capabilities exist, but the core workflow is supported.
