Skip to main content
Glama
Sign In
specter-skills

specter-skills

by dirtcubeinteractive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create battle pass (admin)

specter_create_battlepass

Create a battle pass with tiers for free and premium rewards. Applies to live game config; confirm with user and prefer staging.

Instructions

Create a battle pass. tiers (free/premium rewards per tier) 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>",
      "battlepassId": "<battlepassId>",
      "levelSystemId": "<levelSystemId>"
    },
    "name": "specter_create_battlepass"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
fieldsNoAny other fields for this entity — see the specter-admin skill for the full schema
projectIdNoDefaults to SPECTER_PROJECT_ID
battlepassIdYes
levelSystemIdYesLevel system id that drives tier progression

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate it's not read-only (readOnlyHint=false) and has open world implications (openWorldHint=true). Description adds valuable detail: 'MUTATES live game config' and recommends staging, clarifying side effects and safety. 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?

Two concise sentences with no extraneous information. Front-loaded with 'Create a battle pass.' Each sentence serves a purpose: stating the function and adding behavioral guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and 5 parameters with 60% coverage. Description covers the core function and mutation behavior. References external documentation for `fields`. Could specify return values or error handling, but sufficient for admin tool with cautionary note.

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 coverage is 60% (3 of 5 params have descriptions). Description explains the key `fields` parameter: 'tiers (free/premium rewards per tier) go in `fields`' and references the admin skill for full schema. This adds meaning beyond the schema's generic description.

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?

Clear verb 'Create' and specific resource 'battle pass'. Mention of 'tiers (free/premium rewards per tier) go in `fields`' adds specificity. Distinguishes from many other create_* sibling tools by focusing on battle pass.

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?

States mutation warning: 'MUTATES live game config — confirm with the user and prefer staging.' This provides clear usage context and caution. Does not explicitly name alternatives, but the warning is strong guidance.

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