Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create Tracker issue

tracker_issues_create

Creates a Tracker issue in a specified queue and returns its key, so you can log bugs, tasks, or requests with a summary, description, and fields.

Instructions

Create a Tracker issue; returns the new issue with its key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /issues/`` (create an issue). Covers the common fields; ``extra="allow"`` lets any custom (global or queue-local) field pass through unvalidated. ``type``/``priority`` accept either a bare key string or a ``{"key": ...}`` object (both are valid per the Tracker API); the CLI sends the object form.
notifyNoNotify the users in the fields of the object; omitted, the API notifies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.122.1
    • changedInput schema / properties / body / description
      Previous value: -"Typed request body for ``POST /issues/`` (create an issue).\n\nCovers the common fields; ``extra=\"allow\"`` lets any custom (global or queue-local) field\nkey=value pair pass through unvalidated, matching the CLI's ``-F key=value`` escape hatch.\n``type``/``priority`` accept either a bare key string or a ``{\"key\": ...}`` object (both are\nvalid per the Tracker API); the CLI sends the object form."New value: +"Typed request body for ``POST /issues/`` (create an issue).\n\nCovers the common fields; ``extra=\"allow\"`` lets any custom (global or queue-local) field\npass through unvalidated.\n``type``/``priority`` accept either a bare key string or a ``{\"key\": ...}`` object (both are\nvalid per the Tracker API); the CLI sends the object form."
  2. First observedv0.67.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, destructiveHint=false and non-read-only, so the safety profile is covered. The description adds only the return-value fact ('returns the new issue with its key'), which is useful given no output schema, but says nothing about auth/permission requirements or notification side effects.

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 zero filler. It is arguably too terse for a tool with a nested request body, but it wastes no words.

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?

The one-line return note partially compensates for the absent output schema, and the schema itself is richly described. However, for a create tool with a nested typed body and a notify flag, the description omits queue/permission expectations and any notion of side effects.

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 nested body fields (queue, summary, tags, type, priority, parent, description) are fully documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource ('Create a Tracker issue'), so the agent knows exactly what it does. It does not, however, distinguish itself from overlapping siblings such as tracker_entities_create or tracker_issues_import.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., tracker_entities_create, tracker_issues_import, tracker_issues_update). The agent must infer context entirely from the name.

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