Skip to main content
Glama
Sign In
supercell-mcp

supercell-mcp

by brettadams0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Clash of Clans player

coc_get_player

Retrieve full player statistics from Clash of Clans using a player tag. Get detailed stats including levels, trophies, and more.

Instructions

Full stats for a player by tag (with or without leading #).

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_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description bears full burden but only mentions 'full stats' and tag format. It lacks disclosure of rate limits, read-only nature, error behavior (e.g., invalid tag), or response structure, leaving the agent with minimal behavioral context.

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 sentence with no wasted words, conveying the core purpose and parameter detail efficiently.

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 the simplicity of the tool (one required param, no output schema, no annotations), the description is minimally adequate but leaves gaps: no explanation of what 'full stats' encompasses, no error or edge case handling, and no example usage.

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?

The schema has 0% description coverage for the single 'tag' parameter. The description adds useful context that the tag can include or exclude the leading '#', which is beyond the schema and helps the agent format input correctly.

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 ('Get') and resource ('player'), and clarifies the scope ('Full stats') and tag format. It distinctively separates from sibling tools like coc_get_clan or cr_get_player by game and resource type.

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 when needing player stats by tag, but provides no explicit guidance on when to use or not use this tool compared to alternatives. No exclusions or conditions are stated.

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