Skip to main content
Glama
Sign In
context-crystal

context-crystal

by oswaldo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

crystal_task_transition

Add, complete, remove, or cancel tasks within a crystal to manage task lifecycle and track progress in local AI coding workflows.

Instructions

Add or complete a task in a crystal.

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": {
      "crystal_id": "<crystal_id>",
      "action": "<action>",
      "description_or_id": "<description_or_id>"
    },
    "name": "crystal_task_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction: add, done, remove, or cancel
crystal_idYesCrystal identifier
description_or_idYesTask description (for add) or task ID (for done/remove)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • changedInput schema / properties / action / description
      Previous value: -"Action: add or done"New value: +"Action: add, done, remove, or cancel"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "add",
-  "done"
-]New value: +[
+  "add",
+  "done",
+  "remove",
+  "cancel"
+]
    • changedInput schema / properties / description_or_id / description
      Previous value: -"Task description (for add) or task ID (for done)"New value: +"Task description (for add) or task ID (for done/remove)"
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutating tool. It does not disclose whether task removals/cancellations are reversible, what permissions are required, or what the call returns on success/failure. The verb 'transition' hints at state change but no consequences are described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short, front-loaded sentence with no filler. It is efficient, though its brevity comes at the cost of the omissions noted elsewhere rather than from genuinely complete yet tight phrasing.

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

Completeness2/5

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

For a three-required-parameter mutation tool with no annotations and no output schema, the description should explain the four actions and their effects. Instead it names only two actions and leaves remove/cancel and result behavior unexplained, so an agent cannot fully predict the call's behavior.

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?

Schema description coverage is 100%, so the schema already documents all three parameters and the action enum values. The description adds nothing beyond restating 'add or complete', and its partial action list actually omits remove/cancel. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (add/complete) and resource (task in a crystal), so the core purpose is legible. However, the description is incomplete: the schema supports four actions (add, done, remove, cancel) but the prose only mentions add and complete, omitting remove/cancel entirely. There is no differentiation from any of the many crystal_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus siblings like crystal_goal_transition or crystal_triage, and no prerequisites or exclusions are given. The agent must infer usage entirely from the tool name and schema.

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