specter-skills

Create currency policy (admin)

specter_create_currency_policy

Attach balance limits, currency decay, or earning caps policies to a currency to control player economy. Specify policy type, currency, and required parameters.

Instructions

Attach a policy to a currency: "balance_limits" (min/max a player can hold), "currency_decay" (lose a % over time), or "earning_caps" (max earnable per period). Pass the currency by slug/name. MUTATES live game config — confirm 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": {
      "policyType": "<policyType>",
      "currency": "<currency>"
    },
    "name": "specter_create_currency_policy"
  }
}

Input Schema

Name	Required	Description
`rate`	No	Decay: % per period
`period`	No	Required for decay/earning_caps
`enabled`	No	Required for decay/earning_caps
`currency`	Yes	Currency slug/name the policy applies to
`capAmount`	No	Earning caps: max earnable per period
`projectId`	No
`threshold`	No	Decay: balance below which decay stops
`maxBalance`	No
`minBalance`	No
`policyType`	Yes
`includePurchases`	No
`enforceMaxBalance`	No
`includeConversions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses mutation behavior ('MUTATES live game config') and advises staging, which adds value beyond annotations (readOnlyHint=false, destructiveHint=false). Notes that it changes live configuration, crucial for agent decision-making.

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, front-loaded with key action and policy types, then mutation warning. No wasted words; efficient for quick scanning.

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?

Covers main purpose and mutation risk but lacks details on parameter dependencies per policy type (e.g., which params are required for 'currency_decay'). Given 13 parameters and no output schema, more explicit mapping would improve completeness.

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?

Description mentions policy types and currency identification, partially mapping to parameters (min/max, decay rate, cap). However, with 46% schema coverage, many parameters (e.g., projectId, threshold, includePurchases) are not explained. The description adds some context but not enough to fully compensate for low schema coverage.

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 the tool attaches a policy to a currency, listing three specific policy types (balance_limits, currency_decay, earning_caps). Distinguishes from sibling tools which create other entities. Explicitly mentions the currency identifier (slug/name).

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?

Provides clear context: 'MUTATES live game config — confirm and prefer staging' advises caution and environment preference. However, no explicit comparison to alternative tools, though sibling tools are for different resources so implicit distinction is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server