Skip to main content
Glama
Sign In
Lockstep Core

Lockstep Core

by dandelionrosegroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_ticket

Destructive

Create a new project ticket with an auto-assigned sequential ID to track initiatives, enhancements, refactors, bug fixes, and maintenance work.

Instructions

Create a new ticket with auto-assigned sequential ID.

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": {
      "params": "<params>"
    },
    "name": "create_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=true, idempotent=false, openWorld=false), so the bar is lower. The description adds one useful behavioral fact — that the ID is auto-assigned sequentially — but says nothing about permissions, side effects, or what happens on failure.

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 tight sentence, front-loaded with the action and the one notable behavior. It is efficient but arguably under-specifies for a mutation tool.

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?

An output schema exists, so return values need no explanation. However, for a non-idempotent, destructive create operation with zero schema description coverage and many sibling creation tools, the description omits the required inputs and any routing guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, so the description must carry parameter meaning, and it adds none. It does not mention the required title/type fields, the priority default, or the tags/entity/description options.

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

Purpose4/5

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

States a specific verb (create) and resource (ticket), plus a distinguishing behavioral detail (auto-assigned sequential ID). It does not, however, differentiate itself from the several sibling creation tools (cmd_new_ticket, cmd_bug_fix, create_chain), so an agent still has to infer scope.

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 when-to-use guidance is given. With siblings like cmd_new_ticket, cmd_new_initiative, and cmd_bug_fix, the agent gets no signal about when this generic create_ticket is preferred over the specialized commands.

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