Skip to main content
Glama
Sign In
faida-mcp

faida-mcp

by gabrielmahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nse_equities_guide

Get guided answers on NSE equities for first-time investors. This demo guide explains how to invest in the Nairobi Securities Exchange.

Instructions

Nairobi Securities Exchange guide for first-time investors. 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": "nse_equities_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.9/5.0
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.

Deploy Server

Other Tools