Skip to main content
Glama
Sign In

Orbit

by io.github.Noveum
OverviewDiscussionsAdmin

Create an issue

create_issue

Create an issue on a team. The workflow state defaults to the team first unstarted state. Returns the new issue with its identifier such as "ENG-42".

Input Schema

NameRequiredDescriptionDefault
teamYesTeam key like "ENG", team name, or team id.
cycleNoSprint name, number, id, or "active" for the running sprint.
stateNoWorkflow state name or id on that team.
titleYesOne line summary of the work.
labelsNoLabel names or ids. Replaces the labels already on the issue.
parentNoParent issue, making this a sub issue.
dueDateNoDue date as YYYY-MM-DD.
projectNoProject name, slug or id.
assigneeNoHuman Assignee name, handle, email, id or "me"; use "agent" for self or "agent:<id>" for a Personal Agent.
estimateNoEstimate points.
priorityNoIssue priority, from "urgent" down to "low".
reviewersNoReviewer names, handles, emails, ids, or "me". Replaces the reviewer list.
descriptionNoMarkdown body of the issue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Assignee name, handle, email, id, or \"me\"."New value: +"Human Assignee name, handle, email, id or \"me\"; use \"agent\" for self or \"agent:<id>\" for a Personal Agent."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds valuable behavioral context by specifying that the workflow state defaults to 'unstarted' and clarifies the output format, providing an example identifier ('ENG-42').

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

Conciseness5/5

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

The definition is concise and efficient, using two sentences to explain the function and key behavioral constraints without unnecessary padding.

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

Completeness4/5

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

For a high-complexity tool (13 parameters), the description adequately covers the fundamental operational behaviors, such as default states and result format, allowing an agent to invoke it safely.

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?

Since the schema has 100% coverage and detailed descriptions for all parameters, the description adds no essential semantic meaning beyond what is already explicitly provided in the structured input schema.

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 the primary action (create an issue) and the object (on a team), making its purpose obvious. It is distinct from sibling tools like get_issue or update_issue.

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

Usage Guidelines3/5

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

It doesn't offer explicit guidance on *when* to use this versus a sub-issue creation tool (create_sub_issues), but the mention of default state is a useful contextual clue.

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

All Orbit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources