faida-mcp

diaspora_investment_guide

Identify Kenya diaspora investment options in treasury bonds, NSE equities, and unit trusts to guide capital market decisions.

Instructions

Investment options for Kenya diaspora. DEMO.

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": "diaspora_investment_guide"
  }
}

Input Schema

Name	Required	Description	Default
`location`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 5, 2026

TDQS

C2.2/5.0

Behavior2/5

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

The only behavioral hint is 'DEMO', indicating it's a demonstration, but there is no disclosure about side effects, return format, or how the location parameter affects behavior. With no annotations, the description carries the full burden, and it falls far short.

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

Conciseness3/5

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

The description is extremely concise with zero filler, but it is under-specified and lacks a clear sentence structure. It reads as a fragment rather than a well-formed tool description, making it concise to a fault.

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?

The description provides only a broad topic and lacks details about which investment options are covered, what output to expect, or how the location parameter influences results. Even for a demo, it is incomplete and does not leverage the output schema context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema contains a single parameter 'location' with 0% description coverage, and the description never mentions 'location'. No meaning is added beyond the parameter's name and type, leaving agents without any semantic understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as 'Investment options for Kenya diaspora' but lacks a specific verb like 'provide', 'list', or 'compare'. It reads more like a topic label than an actionable tool description. The 'DEMO' suffix further obscures the actual function.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus sibling tools such as treasury_bond_calculator or nse_equities_guide. The phrase 'for Kenya diaspora' implies a target audience but does not establish clear use cases, prerequisites, or exclusions.

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

Deploy Server