Skip to main content
Glama

stablecoin-yield

by money.barker

barker_vault_position

VAULT POSITION (on-chain read): current redeemable value of a wallet's ERC-4626 vault position. Pass the pool_uid (from barker_executable_pools / barker_execution_quote) and the wallet address; Barker resolves the vault contract and reads balanceOf + convertToAssets directly on-chain, returning shares and current_value in the vault's underlying asset (value_asset, e.g. USDC). Barker does not store your deposit baseline — record the principal you deposited yourself; earned = current_value - your net deposits. Use after depositing via barker_execution_quote to monitor a position: 'how much is my vault position worth now', '我存进金库的 USDC 现在值多少'. (paid: $0.001 per call via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEVM wallet address holding the vault shares (0x + 40 hex)
pool_uidYesBarker pool uid of the ERC-4626 vault, e.g. morpho-vault_base_usdc_0xee8f4ec5 (from barker_executable_pools)

TDQS

A4.6/5.0
Behavior5/5

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

Despite no annotations, description fully discloses on-chain read nature, smart contract calls (balanceOf + convertToAssets), variable resolution from pool_uid, and cost ($0.001 per call). Also warns that Barker does not store deposit baseline.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with purpose first, then details. Includes bilingual example. Slightly long but every sentence is informative.

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?

No output schema, but description explains return values (shares, current_value, value_asset). Covers prerequisites, cost, and data storage limitation. Fully sufficient for agent to use correctly.

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?

Schema has 100% coverage, but description adds value: explains that address is EVM wallet with format, and pool_uid comes from specific sibling tools. Provides context beyond schema.

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 verb 'read' and resource 'vault position', specifies it returns shares and current_value. Ties to sibling tools (barker_executable_pools, barker_execution_quote) for context. Differentiates from other tools by focusing on monitoring positions post-deposit.

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 after depositing via barker_execution_quote to monitor a position' and advises users to track their own principal. Could add more explicit when-not-to-use but is clear enough.

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