Skip to main content
Glama
Sign In
specter-skills

specter-skills

by dirtcubeinteractive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create competition / tournament (admin)

specter_create_competition

Creates a game competition (tournament, instant battle, paid challenge, or bracket) with specified parameters. Modifies live configuration; confirm with user and prefer staging.

Instructions

Create a competition. competitionFormatTypeMasterId: 2=tournament, 3=instant battle, 4=paid challenge, 5=bracket. For match-based (sourceTypeId 1) pass matchId+gameId in fields; entry prices/prizes/schedule also go in fields. MUTATES live game config — confirm with the user and prefer staging.

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": {
      "name": "<name>",
      "competitionId": "<competitionId>",
      "competitionFormatTypeMasterId": "<competitionFormatTypeMasterId>",
      "isSpecialEvent": "<isSpecialEvent>"
    },
    "name": "specter_create_competition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
fieldsNoAny other fields for this entity — see the specter-admin skill for the full schema
projectIdNoDefaults to SPECTER_PROJECT_ID
competitionIdYes
isSpecialEventYes
competitionFormatTypeMasterIdYes2=tournament, 3=instant battle, 4=paid challenge, 5=bracket

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

The description explicitly warns 'MUTATES live game config — confirm with the user and prefer staging.' This adds critical behavioral context beyond the annotations (which show destructiveHint=false), making the risk clear. No contradiction with annotations.

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 two sentences and includes inline explanations. It is front-loaded with the core purpose ('Create a competition') and supplies necessary details without fluff.

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 tool's complexity (6 parameters, nested fields, no output schema), the description covers purpose, usage guidelines, and mutation warning. However, it does not describe the return value or error states, which would be helpful for the agent to handle responses correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%. The description adds meaning for competitionFormatTypeMasterId (maps IDs to types) and the `fields` parameter (explains matchId+gameId usage and entry details). However, other parameters like name, competitionId, and isSpecialEvent lack additional explanation beyond the schema, which only provides types/required status.

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 clearly states 'Create a competition' and explains the different format types (tournament, instant battle, etc.) with specific IDs. This differentiates it from sibling tools like specter_create_battlepass or specter_create_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use specific parameters (matchId+gameId for match-based, entry prices/prizes/schedule in `fields`). It also warns that the tool mutates live game config and recommends user confirmation and staging. However, it does not explicitly distinguish when to use this tool over alternatives like specter_create_event.

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