Skip to main content
Glama

stablecoin-yield

by money.barker

barker_executable_pools

EXECUTION DISCOVERY: which stablecoin vaults in Barker's index support direct deposit/redeem through barker_execution_quote. Returns executable pools with adapter support, live deposit capacity (is_full) and APY/TVL. Call this before barker_execution_quote — every pool listed here can be quoted, and its pool_uid is the exact string that tool expects (its vault_token_address works there too). Skip this call entirely if you already know the vault contract address. All parameters are optional: call with no arguments to get the top executable pools across every asset. APY unit: decimal (0.05 = 5%). Use for 'which pools can my agent actually deposit into', '哪些池子能直接存'. (paid: $0.01 per call via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoOptional stablecoin symbol filter, case-insensitive: usdc, usdt. Omit to list all assets.
chainNoOptional chain filter (lowercase), e.g. base, ethereum
limitNoMax rows (default 20)
queryNoOptional pool keyword, e.g. 'Steakhouse USDC'
actionNoFilter by executable action
min_tvlNoMin TVL floor in USD (default 1000000)

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It discloses cost ($0.01 via x402), APY unit format (decimal), and output compatibility (pool_uid exact string for quote tool). These are valuable behavioral traits beyond any structured metadata.

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 front-loaded with 'EXECUTION DISCOVERY' and each sentence adds unique value: purpose, relationship to quote tool, output, skip condition, optionality, APY unit, use cases, and cost. Dense but well-structured with no redundancy.

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?

For a discovery tool with 6 optional params and no output schema, the description covers key output fields, operational workflow, cost, and APY semantics. It is complete enough for an agent to select and invoke the tool correctly.

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 description coverage is 100%, so baseline is 3. The description adds that all parameters are optional and explains the no-argument behavior, but does not provide additional parameter-specific semantics beyond what the schema already states.

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 opens with 'EXECUTION DISCOVERY' and explicitly states it identifies stablecoin vaults supporting direct deposit/redeem through barker_execution_quote. It clearly distinguishes this from siblings by referencing the specific workflow and output fields (adapter support, is_full, APY/TVL).

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

Usage Guidelines5/5

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

Provides explicit when/when-not: 'Call this before barker_execution_quote' and 'Skip this call entirely if you already know the vault contract address.' Also clarifies that all parameters are optional and that no-arg calls return top executable pools, giving clear invocation context.

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

All stablecoin-yield toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: yield recommendation, pool listing, execution discovery, quoting, detail/history, market data, cross-chain routes, and position monitoring. No two tools overlap in functionality.

Naming Consistency5/5

All tools follow the consistent pattern 'barker_<domain>_<action>' using snake_case. The naming is descriptive and predictable, making it easy for an agent to understand the purpose of each tool.

Tool Count5/5

With 11 tools, the server covers the entire stablecoin yield workflow without being bloated. Each tool contributes to discovery, execution, monitoring, or market analysis, and none feel superfluous.

Completeness5/5

The tool set provides end-to-end coverage for stablecoin yield management: from discovery and analysis to execution and position monitoring. Missing features like batch position queries are outside the server's stated scope.

Resources