historia-mcp

ethnic_groups_guide

Discover Kenya's major ethnic groups, cultures, and communities. Access detailed guides on cultural heritage and historical context.

Instructions

Kenya major ethnic groups, cultures, and communities. 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": "ethnic_groups_guide"
  }
}

Input Schema

Name	Required	Description	Default
`group`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.4/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 states it is a 'DEMO', implying limited or non-production data, but does not explain read-only behavior, return format, or any constraints beyond the parameter.

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 brief, but lacks necessary detail. While it is front-loaded, it omits key information about the parameter and usage, making it underspecified rather than efficiently concise.

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?

Given the presence of an output schema, the description does not need to detail return values, but it fails to explain what the tool does with the parameter or how it ties into the sibling context. A demo tool still requires clarity on its functionality.

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 provides zero description for the 'group' parameter, and the tool description offers no explanation of its purpose, expected values, or how it affects results. This leaves the agent completely uninformed.

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 to Kenya's major ethnic groups, cultures, and communities. It distinguishes from sibling tools like cultural_heritage_sites, which focus on locations rather than groups. However, the inclusion of 'DEMO' introduces ambiguity about its reliability.

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. The description does not indicate suitable contexts or prerequisites, leaving the agent without decision criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server