Skip to main content
Glama
Sign In
specter-skills

specter-skills

by dirtcubeinteractive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Stop an achievement (admin)

specter_stop_achievement

Stop a live achievement task or task group while keeping the record. Resume later by scheduling the task again.

Instructions

Halt a live task or task-group (keeps the record; reversible by scheduling again). Pass exactly one of taskRef / groupRef. MUTATES live game config — confirm and prefer staging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "specter_stop_achievement"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskRefNo
groupRefNo
projectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Discloses mutation ('MUTATES live game config'), non-destructiveness ('keeps the record; reversible by scheduling again'), aligning with annotations (readOnlyHint=false, destructiveHint=false). Adds value by explaining reversibility.

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 efficient sentences with no redundancy. First sentence states core action and exclusive parameter choice; second adds caution and advice. Every word 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?

Given no output schema and 0 required params, description covers purpose, usage, and behavioral traits. Could elaborate on effects on players or state after stopping, but current level is sufficient for a straightforward tool.

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?

With 0% schema coverage, description partially compensates by mentioning taskRef/groupRef and the exclusive choice. However, does not explain what these references are or describe projectId. Meaning added but incomplete.

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 'Halt a live task or task-group (keeps the record; reversible by scheduling again)'. Uses specific verb 'halt' and identifies the resource (task/group). Distinguishes from siblings like specter_schedule_achievement and specter_delete_achievement.

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 explicit instruction to pass exactly one of taskRef/groupRef. Advises caution with 'MUTATES live game config — confirm and prefer staging'. Lacks explicit when-not-to-use or comparison to alternatives, but sufficient given context.

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