@ethioviral/mcp

List catalog categories

list_categories

Lists all product categories (airtime, esim, giftcards, gaming, bills) with their item counts for quick browsing.

Instructions

Returns each product category (airtime, esim, giftcards, gaming, bills) with its item count.

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": "list_categories"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 16, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries full responsibility. It discloses the primary behavior (returns categories with counts) and implicitly indicates a read operation ('returns'), but it does not mention any potential side effects, authentication requirements, rate limits, or output format details. For a simple list operation, this is acceptable but not comprehensive.

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, front-loaded sentence that immediately states the action and resource. It lists the categories concisely and avoids unnecessary fluff. Every word serves a purpose, making it highly efficient.

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

Completeness4/5

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

For a tool with no parameters and no output schema, the description covers the essential function: returning all categories with counts. However, it does not describe the return format (e.g., array vs. object, field names), which could be helpful. Given the simplicity of the operation, this is a minor gap and the description is largely complete.

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?

There are zero parameters and schema coverage is 100% (vacuously), so there are no parameter semantics to explain. The description adds no parameter-related information, which is appropriate given the absence of parameters. Baseline for 0 parameters is 4.

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

Purpose5/5

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

The description clearly states the verb 'returns' and the resource 'each product category', listing the exact categories (airtime, esim, giftcards, gaming, bills) and the associated item count. This makes the tool's purpose unambiguous and distinct from siblings like get_category (single) or list_premium_products (premium-only).

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 description states what the tool does but does not explicitly mention when to use it versus alternatives. The context implies it is for retrieving all categories, but there is no guidance such as 'use get_category for a single category' or 'use search_catalog for filtering'. The usage is inferred, not explicit.

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