Skip to main content
Glama
gabrielmahia

faida-mcp

by gabrielmahia

nse_ipo_guide

Participate in Kenya IPOs with this step-by-step guide. Learn the NSE IPO process, eligibility, timelines, and requirements to buy shares during initial public offerings.

Instructions

Kenya Initial Public Offering (IPO) participation guide. DEMO.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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.

Install Server

Other Tools

Latest Blog Posts

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