Skip to main content
Glama
talhaorak

Taiga MCP Bridge

by talhaorak
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

create_issue

Create a new issue in a project by providing subject, priority, status, severity, and type. Optional verbosity controls response detail.

Instructions

Creates a new issue within a project. verbosity: 'minimal', 'standard' (default), 'full'. Uses default session if session_id not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
subjectYes
priority_idYes
status_idYes
severity_idYes
type_idYes
kwargsNo
session_idNo
verbosityNostandard

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changedv2.0.1
    • addedInput schema / properties / kwargs / default
      Added value: +null
    • changedInput schema / properties / kwargs / title
      Previous value: -"kwargs"New value: +"Kwargs"
    • removedInput schema / properties / kwargs / type
      Removed value: -"string"
    • addedInput schema / properties / session_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / session_id / default
      Added value: +null
    • removedInput schema / properties / session_id / type
      Removed value: -"string"
    • addedInput schema / properties / verbosity
      Added value: +{
+  "default": "standard",
+  "title": "Verbosity",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "project_id",
-  "subject",
-  "priority_id",
-  "status_id",
-  "severity_id",
-  "type_id",
-  "kwargs"
-]New value: +[
+  "project_id",
+  "subject",
+  "priority_id",
+  "status_id",
+  "severity_id",
+  "type_id"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "additionalProperties": true,
+      "title": "Result",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "create_issueOutput",
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the burden falls on the description. It mentions verbosity levels and default session behavior, but does not disclose side effects, authorization needs, or other behavioral traits beyond 'creates'.

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?

Two concise sentences with no redundancy. The first sentence states purpose, the second adds parameter details. However, it could be slightly more structured.

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?

Despite having an output schema, the description does not cover many required parameters or provide usage context for the variety of parameters. It leaves major gaps for an agent to invoke correctly.

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 0%, so description must compensate. It explains verbosity and session_id, but leaves other 7 parameters unexplained, including required IDs. This is insufficient for a tool with 9 parameters.

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?

The description clearly states it creates a new issue within a project, using specific verbs and resource. However, it does not differentiate from sibling create tools like create_epic or create_task, which would help an agent choose correctly.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description lacks explicit when-to-use recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/talhaorak/pytaiga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server