faida-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.3
Disambiguation4/5
Each tool targets a distinct Kenya-focused financial topic (treasury bonds, equities, unit trusts, diaspora, IPOs, general literacy), so they are mostly clear. However, 'nse_equities_guide' and 'nse_ipo_guide' share some conceptual overlap, and 'financial_literacy_kenya' could be seen as a catch-all, but descriptions are specific enough to avoid confusion.
Naming Consistency4/5
All names use lowercase with underscores and follow a [topic]_[suffix] pattern. The suffixes vary ('calculator', 'guide', 'comparison') rather than being uniform, which is a minor inconsistency, but the overall structure is predictable and readable.
Tool Count5/5
With 6 tools, the set is well-scoped for a Kenya investment education server. It covers major asset classes and investor personas without being overly large or too thin.
Completeness4/5
The tools cover a solid range of Kenya investment topics (bonds, equities, unit trusts, IPOs, diaspora, fundamentals). Minor gaps exist (e.g., real estate, forex, or retirement planning are absent), but for a demo/educational server, this is a reasonable surface.
Average 2.7/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 32 commits in the last 12 weeks
- Last stable release on July 18, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

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.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavior itself, but it only states content and 'DEMO'. It does not explain what happens with the topic parameter, expected output, or any limitations, leaving significant behavioral ambiguity.
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 text is very brief but not effectively structured; it is a sentence fragment followed by 'DEMO'. It is concise but under-specified, lacking the clarity that a well-formed description should have.
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 being a simple tool with an output schema, the description omits essential usage context—how to invoke it, what to expect in the response, and what 'DEMO' entails. It feels incomplete even for a glossary tool, leaving the agent to guess at functionality.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single 'topic' parameter has 0% schema description coverage and the description offers no guidance on valid values or how it affects results. The name is somewhat self-explanatory, but the description fails to compensate for the lack of schema detail.
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 content area ('Kenya personal finance fundamentals and glossary') but lacks a clear verb like 'provides' or 'explains'. It distinguishes from sibling tools only by being broad and general, not by specific function, and 'DEMO' suggests it may be incomplete.
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 given on when to use this tool versus the related siblings (e.g., treasury_bond_calculator, nse_equities_guide). The 'DEMO' label hints at limited use but provides no explicit context or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it only says 'guide. DEMO.' It does not disclose whether the tool returns static content, if it has limitations, or what the user should expect. The 'DEMO' marker hints at incompleteness but offers no explicit behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While the description is extremely short, it is under-specified. The phrase 'Kenya Initial Public Offering (IPO) participation guide. DEMO.' is a single flat fragment that lacks enough substance to help an agent decide. It is not a tautology but feels more like a placeholder than an informative description.
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?
Although there are no parameters and an output schema exists, the description fails to convey what kind of guide content is returned or how it differs from other NSE guides. The 'DEMO' tag also introduces uncertainty about whether the guide is authoritative or fully functional.
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?
The tool has zero parameters and the schema is empty, so the description adds no parameter details. Given the rule that 0 params baseline is 4, the schema already covers everything and the description does not need to compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as a 'Kenya Initial Public Offering (IPO) participation guide,' which specifies the subject and resource. It is not a tautology and has a clear focus, though it does not explicitly differentiate from sibling guides like nse_equities_guide.
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 alternatives such as treasury_bond_calculator or nse_equities_guide. The description simply states what the tool is, without any contextual triggers, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It only says 'guide' and 'DEMO,' which hints at a non-production/demo nature but does not disclose whether the tool is read-only, what the query does, or any side effects—leaving significant behavioral unknowns.
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 a single sentence that is front-loaded with the key information (NSE, target audience). It is suitably concise with no wasted words, and 'DEMO' adds useful context without bloating.
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?
While an output schema exists, the description alone is insufficient for an agent to infer invocation details, expected query semantics, or how this tool differs from sibling guides. It leaves key gaps in operational understanding and is therefore not complete enough for a tool with zero annotations.
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 has one 'query' parameter with no description (0% coverage). The tool description does not mention the parameter at all, so it adds no meaning about what value to provide or how it affects the result.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the domain (Nairobi Securities Exchange) and target audience (first-time investors), distinguishing it from sibling tools. However, it lacks a strong action verb; 'guide' is a noun and the intended operation is implied rather than explicitly stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for first-time investors' provides implied usage context. It does not explicitly mention alternatives or when not to use this tool, leaving some ambiguity relative to sibling guides like nse_ipo_guide or financial_literacy_kenya.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. 'DEMO' signals a demo mode, but it does not explain data freshness, limitations, or how typical returns are derived, leaving significant ambiguity.
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 a single concise sentence plus the 'DEMO' label, front-loaded with the core purpose and free of unnecessary words. It is highly scannable and efficient.
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?
An output schema exists, reducing the need to explain return values. However, the description omits how risk_profile influences the comparison and what 'typical returns' means, making it adequate for a simple demo tool but incomplete for deeper understanding.
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 only parameter, risk_profile, is not mentioned in the description, and the schema has no description either. With 0% schema coverage, the description adds no meaning to the input parameter.
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 uses a clear verb 'Compare' and specifies the resource 'Kenya unit trust fund types and typical returns.' This distinguishes it from sibling tools like nse_equities_guide and treasury_bond_calculator, which cover different investment products.
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?
There is no guidance on when to use this tool versus alternatives, nor any scenario-based recommendations. The 'DEMO' label hints at non-production use but does not explicitly state when to invoke or avoid the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations to describe safety or side effects. The description only adds 'DEMO,' which hints that it may be a demonstration or limited in functionality, but it does not disclose what the tool does under the hood, how results are calculated, or any limitations beyond the demo label. With zero annotations, the description carries the full burden, and this is insufficient.
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 a single sentence with no wasted words. It front-loads the purpose ('Kenya Treasury bond yield and return calculator') and adds a meaningful qualifier ('DEMO'). It is appropriately sized for the tool's simplicity and does not repeat any schema or annotation information.
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?
For a calculator with three parameters and no parameter descriptions in either schema or description, the tool is under-specified. The output schema exists, so return values are covered, but the description omits input semantics, usage context, and any explanation of the 'DEMO' status. It barely meets the minimum for a usable description.
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?
Schema description coverage is 0%, and the description does not mention any of the three parameters (principal_kes, tenor_years, coupon_rate_pct). While parameter names are somewhat self-explanatory, the description adds no meaning about units, defaults, or how they affect the calculation. It completely fails to compensate for the lack of schema descriptions.
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's function: 'Kenya Treasury bond yield and return calculator.' It uses a specific verb ('calculator') and resource ('Kenya Treasury bond yield and return'), and clearly distinguishes itself from sibling tools that are informational guides rather than calculators.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for calculating yields/returns on Kenyan treasury bonds, and its 'DEMO' label signals a limited-use context. However, it does not explicitly state when to use this tool versus alternatives (e.g., comparing with equity guides), nor does it mention any prerequisites or exclusions, so it only offers implied usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![faida-mcp MCP server](https://glama.ai/mcp/servers/gabrielmahia/faida-mcp/badges/card.svg)](https://glama.ai/mcp/servers/gabrielmahia/faida-mcp)

Score Badge

Copy to your README.md:

[![faida-mcp MCP server](https://glama.ai/mcp/servers/gabrielmahia/faida-mcp/badges/score.svg)](https://glama.ai/mcp/servers/gabrielmahia/faida-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrielmahia/faida-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server