F
licenseA
qualityC
maintenanceEnables AI agents to discover verifiable DeFi yield opportunities, generate algorithmic portfolio plans, and track cryptographic proof receipts, bridging LLMs with blockchain yield protocols.
9
YIELD INTELLIGENCE — Passive Income MCP
Server Details
Passive income opportunity scanner. Yield analysis and portfolio optimization for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- thebrierfox/intuitek-ace
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.7/5.0
Tool DescriptionsA
Average 3.7/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: one identifies opportunities across asset classes, the other builds and rebalances a portfolio. No overlap in functionality.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern: analyze_yield_opportunities and optimize_income_portfolio.
Tool Count3/5
Only 2 tools for a domain that typically requires more granular operations (e.g., specific asset analysis, execution, monitoring). The scope feels a bit thin.
Completeness2/5
The tools cover high-level analysis and optimization but lack execution, tracking, or individual asset management, leaving significant gaps for a full passive income workflow.
Available Tools
2 toolsanalyze_yield_opportunitiesYield Opportunity AnalyzerARead-onlyIdempotentInspect
Identify the highest-returning passive income opportunities across asset classes. Use when the user wants to generate passive income, maximize portfolio yield, or find dividend and interest-bearing investments.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| risk_tolerance | No | ||
| investment_capital | Yes | Available capital in USD | |
| monthly_income_target | No | Target monthly passive income in USD |
Tool Definition Quality
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds no behavioral context beyond 'Identify'. This is acceptable but not extra informative.
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, front-loaded with the core action, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so agent lacks info on return format. Description covers purpose and usage but not what the tool returns. Adequate for simple identification tool but could be more complete.
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 67% with two parameters described. The description mentions 'passive income' but does not elaborate on parameter roles (e.g., how risk_tolerance affects results). Adequate but not exceptional.
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?
Description clearly states the tool identifies highest-returning passive income opportunities across asset classes. The verb 'Identify' and resource 'opportunities' are specific, and the tool is distinct from sibling 'optimize_income_portfolio'.
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?
Description explicitly says when to use the tool: when user wants passive income, yield maximization, or dividend/interest investments. However, it does not mention when not to use it or compare with the sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
optimize_income_portfolioIncome Portfolio OptimizerBRead-onlyIdempotentInspect
Build and rebalance a diversified portfolio to maximize recurring income. Use when the user wants to achieve financial independence through investment income or optimize an existing portfolio for yield.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| current_holdings | No | Current portfolio positions | |
| time_horizon_years | No | Investment time horizon in years | |
| target_monthly_income | Yes | Desired monthly income in USD |
Tool Definition Quality
B3.4/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description claims the tool 'builds and rebalances' a portfolio, implying write/mutation operations. However, annotations declare readOnlyHint=true and destructiveHint=false, indicating a read-only, idempotent operation. This direct contradiction misleads agents about the tool's behavior.
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 sentences, front-loaded with the purpose, and contains no unnecessary words. Every sentence adds value and is efficiently structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite good purpose clarity, the description is incomplete. It omits details about the output (no output schema) and fails to disclose the read-only nature contradicting annotations. Given the contradiction and missing return value info, the description does not fully equip an agent to use 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 the schema already explains all parameters. The description adds no additional parameter details beyond what the schema provides, meeting the baseline for this dimension.
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 tool builds and rebalances a diversified portfolio to maximize recurring income, with a specific verb and resource. It distinguishes from the sibling 'analyze_yield_opportunities' by focusing on actual portfolio construction rather than just analysis.
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 states 'Use when the user wants to achieve financial independence... or optimize an existing portfolio for yield.' This provides clear context for when to invoke the tool, though it does not explicitly exclude use cases or mention the sibling tool as an alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to discover, evaluate, and execute DeFi yield strategies across EVM and Solana chains through natural conversation, with transactions signed locally.15101
- AlicenseAqualityCmaintenanceCross-chain DeFi intelligence MCP server for AI agents. 7 tools for yield discovery, pool analysis, profit simulation, risk scoring, whale tracking, impermanent loss calculation, and DeFi overview across 86 chains and 6,500+ liquidity pools.71AGPL 3.0
- AlicenseAqualityAmaintenanceReal-time stablecoin yield index across DeFi protocols and CEX earn programs, with an AI yield advisor, risk signals and non-custodial deposit/redeem quotes for AI agents. Ships agent skills and a self-host stdio wrapper alongside the hosted remote MCP with x402 pay-per-call.4623MIT
