Project Tracker MCP Server

by spranab

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

create_issue

Create a new issue or bug in a project. Specify title, priority, severity, and metadata to track and resolve problems.

Instructions

Create a new issue/bug in a project

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": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "create_issue"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No	Tags for categorizing issues
`title`	Yes	Title of the issue
`metadata`	No	Additional metadata (stack trace, version, etc.)
`priority`	No	Priority level	medium
`severity`	No	Severity level	medium
`issue_type`	No	Type of issue	bug
`project_id`	Yes	UUID of the project this issue belongs to
`assigned_to`	No	Person assigned to fix the issue
`description`	No	Detailed description of the issue
`environment`	No	Environment where issue occurred (production, staging, dev)
`reported_by`	No	Person who reported the issue

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/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 burden. It implies a write operation but does not disclose permissions, side effects, required fields, defaults, or whether creation is reversible. For an 11-parameter mutation tool, this is a significant transparency gap.

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 front-loaded sentence with no wasted words. It is efficient, though very terse for an 11-parameter mutation tool, and offers no additional structured context.

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?

Given 11 parameters, no annotations, no output schema, and a create/mutation operation, the description is too sparse. It omits required fields, defaults, response behavior, and any caveats an agent would need before invoking the 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?

Schema description coverage is 100%, so all 11 parameters, including enums and defaults, are already documented in the schema. The description adds no parameter-level meaning, syntax, or constraints beyond that, making the baseline 3 appropriate.

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 ('issue/bug') scoped to a project, which lets an agent distinguish it from sibling creation tools like create_epic and create_story. However, it does not explicitly name those alternatives or further differentiate 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?

Provides no guidance on when to use this tool versus alternatives such as create_epic or create_story, and no prerequisites (e.g., project_id required) or exclusions. Usage is only implied by the tool and resource names.

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