Skip to main content
Glama
Sign In
nishati-mcp

nishati-mcp

by gabrielmahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

kplc_connection_guide

Guide users through the process of applying for a new KPLC electricity connection in Kenya, including required information by county and connection type.

Instructions

Guide to new KPLC electricity connection in Kenya. 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": "kplc_connection_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNo
connection_typeNoresidential

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

The description includes 'DEMO', which suggests non-production behavior but is vague. No other behavioral traits like safety, side effects, or limitations are disclosed.

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 very concise, but it lacks structure and omits essential details. It achieves conciseness at the expense of completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given two parameters, no schema descriptions, no annotations, and an output schema, the description is grossly incomplete. It fails to explain how to use the tool or what results to expect.

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 description does not mention any parameters, and the input schema has no descriptions (0% coverage). It adds no meaning beyond the property names.

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 guide for new KPLC electricity connections in Kenya. This is a specific verb-resource combination that distinguishes it from sibling tools like energy_rights_query or tariff_calculator.

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. There is no indication of prerequisites or context of use.

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