castle-clash-mcp

Overview Schema Source Related Servers Discussions Admin

list_catalog

Retrieve all entries for any Castle Clash catalog category, including pets, crests, traits, buildings, and more. Specify a category and optional limit to get the full list.

Instructions

List all entries in a catalog category (e.g. pet, crest, trait, signature, buildings, decorations, dungen, watchers, slime, talent, enchantment).

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

Input Schema

Name	Required	Description	Default
`limit`	No
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It conveys a read-only list operation, but it fails to disclose that the optional limit defaults to 300, which creates tension with the promise of listing 'all' entries. No mention of pagination, ordering, or payload size is provided.

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 with no filler. The verb and object appear first, and the category examples are packed into parentheses without bloating the core message.

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

Completeness3/5

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

For a simple list operation, the primary use case and expected result are mostly clear. However, the description is incomplete because it omits the effect of limit, does not direct users to list_categories for valid category names, and no annotations or output schema fill those gaps.

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 gives helpful examples for the category parameter, but it says nothing about the limit parameter and does not explain how limit interacts with the 'all entries' behavior.

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 uses a specific verb ('List'), a clear resource ('entries in a catalog category'), and a rich set of example categories. It is immediately distinguishable from siblings like get_catalog_entry and list_categories.

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 clearly scopes the tool to listing catalog entries and gives representative category values, so usage context is inferable. However, it never explicitly says when to prefer this tool over alternatives such as get_catalog_entry for a single entry or list_categories for category names.

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