Skip to main content
Glama
Sign In
supercell-mcp

supercell-mcp

by brettadams0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get current war

coc_get_current_war

Get a clan's current war status from Clash of Clans. Provide the clan tag; works only for publicly visible wars.

Instructions

A clan's current war status (if public / not in private war log).

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": {
      "tag": "<tag>"
    },
    "name": "coc_get_current_war"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. The only behavioral insight is the privacy condition. Missing details like authentication requirements, rate limits, or error handling for invalid tags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence of 14 words with no fluff. Efficient but could include more structured guidance without lengthening significantly.

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?

Low complexity (1 parameter, no output schema). The description covers the core function and one caveat, but lacks detail on return structure or edge cases, which is acceptable for a minimal tool.

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?

Only one parameter ('tag') with zero schema description coverage. The description does not explain the parameter format (e.g., clan tag example) or its role, relying solely on the parameter name.

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 name and title 'Get current war' clearly indicate the action. The description specifies retrieving a clan's current war status and includes a condition (public vs private war log), which distinguishes this tool from siblings like coc_get_clan or coc_get_player.

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?

No guidance on when to use this tool versus alternatives (e.g., coc_get_clan for general clan info). No prerequisites or context for when the war log might be private.

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