@ethioviral/mcp

List products in a category

get_category

Fetches every product in a specified category from Ethio-Viral's live catalog, enabling browsing of available gift cards, subscriptions, and SMM services.

Instructions

Returns every product in one category (from list_categories).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "get_category"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 16, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation is a read ('Returns') but doesn't disclose pagination, ordering, error behavior, or whether the category must be an exact ID from list_categories. The reference to list_categories adds some context but not enough for a tool with zero annotation coverage.

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?

One sentence, front-loaded with the action and scope, and the parenthetical reference to list_categories is efficient. No wasted words.

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?

For a simple single-parameter read tool, the description is minimal but lacks key context: no output schema, no pagination info, no error behavior, and no guidance on how the category value relates to list_categories output. The sibling list includes search_catalog and list_premium_products, so more routing context would help.

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. It mentions the category comes from list_categories, which adds meaning beyond the bare 'category' string property, but it doesn't explain the expected format (ID vs name) or how to obtain it beyond the parenthetical reference.

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 states a specific verb ('Returns') and resource ('every product in one category'), and references list_categories as the source of category values. It is clear what the tool does, though it doesn't explicitly distinguish it from sibling tools like search_catalog or get_product.

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 implies usage context by noting the category comes from list_categories, which tells the agent where to get valid input. However, it doesn't explicitly state when to use this tool versus alternatives like search_catalog or list_premium_products.

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