Skip to main content
Glama
Sign In
nishati-mcp

nishati-mcp

by gabrielmahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

energy_subsidy_programs

Find energy subsidy and access programs in Kenya for rural electrification and off-grid solar, filtered by county.

Instructions

Kenya energy subsidy and access programs. 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": "energy_subsidy_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions subject matter and 'DEMO', omitting any details about what the tool does, side effects, or requirements. This is insufficient for an agent to understand behavior.

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 concise but lacks structure. While it is short, it fails to convey essential information, making brevity detrimental rather than helpful.

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 having an output schema and a simple input schema, the description provides almost no context. It does not explain what the tool returns or how to use it, leaving the agent underinformed.

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?

Schema description coverage is 0%, so the description must compensate. The sole parameter 'county' is not described at all in either the schema or the tool description, leaving its semantics unknown.

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

Purpose2/5

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

The description 'Kenya energy subsidy and access programs. DEMO.' is vague about what the tool does. It does not specify the action (e.g., list, query, apply) and does not distinguish it from sibling tools like 'energy_rights_query' which also deals with energy topics.

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 its siblings. The word 'DEMO' might imply demonstration purposes but is not explicit, leaving the agent without clear usage context.

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