Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coc_clan_members

Read-onlyIdempotent

Fetch all members of a Clash of Clans clan by clan tag to review roster and membership details.

Instructions

Get members of a Clash of Clans clan.

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": {
      "clanTag": "<clanTag>"
    },
    "name": "coc_clan_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
clanTagYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructiveness, so the safety profile is covered elsewhere. The description adds nothing about pagination, member-count caps, result ordering, or authentication beyond the implicit, which is the remaining value it should provide.

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?

One short sentence, front-loaded and free of filler, which is structurally sound. But the brevity comes at the cost of under-specification rather than efficiency.

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?

No output schema exists, so the description should hint at what a member record contains (roles, trophies, donations) and whether the full roster or a capped list is returned. With zero parameter documentation and no return-shape context, an agent has to discover behavior by trial.

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 and it does not. It never mentions clanTag (no format hint such as the leading '#' or URL-encoding) or what api_key is for, leaving both parameters undocumented anywhere.

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

Purpose4/5

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

States a specific verb and resource ('Get members of a Clash of Clans clan'), which is clear enough for an agent to know what it retrieves. It does not differentiate from nearby siblings such as coc_clan (which presumably returns clan details) or coc_player, so an agent must guess which of the CoC tools to pick.

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 statement of when to use this versus coc_clan, coc_player, or the Clash Royale/Brawl Stars siblings. There is no guidance on prerequisites such as needing a valid clan tag or API key.

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