Skip to main content
Glama
Sign In
specter-skills

specter-skills

by dirtcubeinteractive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create bundle / loot box (admin)

specter_create_bundle

Create a game bundle for gacha/loot box sets with pity fields. Mutates live config; prefer staging and confirm with user.

Instructions

Create a bundle. For a gacha/loot box set isGacha + pity fields in fields; contents/prices go in fields too. 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>",
      "typeId": "<typeId>"
    },
    "name": "specter_create_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
fieldsNoAny other fields for this entity — see the specter-admin skill for the full schema
typeIdYesBundle type id
projectIdNoDefaults to SPECTER_PROJECT_ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description adds value beyond annotations by specifying that the tool mutates live game config and advising confirmation and staging preference. Annotations indicate readOnlyHint=false but do not convey the severity (live config mutation). 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 sentences with no wasted words. The first sentence front-loads the core action, and the second adds essential behavioral nuance and parameter hints. Every sentence earns its place.

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?

For a mutation tool without output schema, the description covers the key patterns (gacha/pity) and safety advice. However, the `typeId` parameter is not explained, and the `fields` parameter points to an external reference. Minor gaps but overall adequate for admin tool.

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?

With 75% schema coverage, the description provides essential guidance for the `fields` parameter (e.g., isGacha, pity, contents, prices), which is not detailed in the schema. This adds significant meaning for bundle creation, though the fields description still references an external skill for full schema.

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 the tool creates a bundle, with specific use cases for gacha/loot boxes (isGacha, pity fields). It distinguishes from many sibling create_* tools by focusing on bundles and noting admin context in the title.

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?

Explicitly says 'MUTATES live game config — confirm with the user and prefer staging,' providing clear context for when to use and caution. Does not explicitly mention when not to use or compare to alternatives, which is acceptable given the detailed mutation warning.

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