castle-clash-mcp

by mmadersbacher

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_system

Fetch rows from a specified Castle Clash game system, with English annotations for clear interpretation.

Instructions

Rows of a game system (see game_systems). English-annotated (name_en).

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": {
      "system": "<system>"
    },
    "name": "get_system"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

C2.2/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 burden of behavioral disclosure. It adds one useful detail (English-annotated via name_en) but does not mention return format, pagination/limit behavior, error cases, or any side effects. This is a minimal disclosure for a data-fetching tool.

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 very short and contains no filler, but it is a cryptic fragment rather than a clear, front-loaded definition. It earns its place as a hint but is too terse to be considered well-structured guidance.

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 no annotations, no output schema, and sparse parameter docs, the description should compensate by explaining the system identifier, the meaning of rows, and the limit parameter. The sibling context includes several similar get_* tools, and this description does not clarify how get_system fits among them.

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?

Schema description coverage is 0%, so the description must explain what the system and limit parameters mean. It does not address either parameter; 'English-annotated (name_en)' hints at an output field but not how to fill in the required system argument.

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

Purpose3/5

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

The description identifies the resource ('game system') and a concrete verb ('get'), but 'Rows of a game system' is vague about what is actually returned. It points to game_systems for context but does not clearly distinguish this from sibling tools like game_systems or system_lookup.

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?

The only usage guidance is 'see game_systems,' which hints at a relationship but provides no explicit when-to-use or when-not-to-use instructions. No alternatives are named, and the tool's role relative to similar sibling tools is left to inference.

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