Skip to main content
Glama
Sign In
castle-clash-mcp

castle-clash-mcp

by mmadersbacher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

refresh_data

Rebuild the database by loading the seed catalog and scraping casclash for current hero data. Use seed_only to skip scraping or set a limit to cap heroes processed.

Instructions

Rebuild the database: load seed catalog and (unless seed_only) scrape casclash. limit caps heroes scraped.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
seed_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 the burden. It discloses the core behavior: rebuilding the database, loading the seed catalog, and scraping casclash unless seed_only is set. However, it does not explicitly warn that this likely overwrites/destroys existing data, nor does it mention runtime, network dependence, or auth requirements.

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 dense, front-loaded sentence conveys the main purpose and parameter behavior without filler. Every phrase earns its place.

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?

Given there is no output schema and no annotations, the description leaves some gaps: no mention of return behavior, no explicit destructive-data warning, and no operational caveats such as duration or required permissions. It covers the input semantics well but is not fully complete for a database-rebuilding tool.

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?

Schema description coverage is 0%, but the description directly explains both parameters: seed_only toggles scraping off, and limit caps the number of heroes scraped. This adds meaningful semantics beyond the bare schema types and defaults.

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 starts with the specific verb phrase 'Rebuild the database', clearly identifying the resource and the operation. It further specifies the two main actions (load seed catalog, scrape casclash) and the conditional behavior, which distinguishes it from the many read-only sibling tools.

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 description explains what the tool does but gives no guidance on when to use it versus alternatives, nor any conditions or exclusions. There is no mention of how this relates to the other data tools or when a caller should prefer seed_only vs full scrape.

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

Deploy Server

Other Tools