Skip to main content
Glama
Sign In
specter-skills

specter-skills

by dirtcubeinteractive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create store (admin)

specter_create_store

Create a store with categories, contents, and platforms. Mutates live game config; confirm with user and use staging first.

Instructions

Create a store. Categories/contents/platforms go in fields (storeCategories[]). 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>",
      "storeId": "<storeId>"
    },
    "name": "specter_create_store"
  }
}

Input Schema

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

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 mutation (readOnlyHint=false) and description reinforces 'MUTATES live game config', adding caution about user confirmation and staging preference. This provides useful behavioral context beyond 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 wasted words. First sentence states function, second provides critical warning. Efficient and front-loaded.

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?

Given the tool's mutation nature and zero output schema, the description covers purpose, usage caution, and a key parameter hint. It references an external skill for full schema, which is acceptable but slightly vague. Complete enough for a creation 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?

Schema coverage is 75%, and the description adds meaning for the `fields` parameter by specifying its content (storeCategories[]). Other parameters are documented in schema. This adds value for a key parameter.

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?

Clearly states 'Create a store' identifying the verb and resource. The description adds context about categories/contents/platforms going into `fields`, making it distinct from other specter_create_* tools for different entities.

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?

Gives explicit guidance: 'confirm with the user and prefer staging' due to mutation of live config. This helps the agent decide when to use the tool responsibly. Lacks explicit exclusions or comparison to alternatives, but context is clear.

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