Skip to main content
Glama

File an error issue in GitHub, Linear or Jira

create_ticket

Create a ticket for an error issue in GitHub Issues, Linear or Jira (connected on the Tools tab). The body is short and redacted. One GitHub issue per error issue. Only works when the app allows MCP writes.

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

Input Schema

NameRequiredDescriptionDefault
issue_idYes
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the ticket body is auto-generated, short and redacted (so the agent shouldn't expect to author content or see full error data), that GitHub tickets are one-per-error-issue, and that MCP writes must be enabled. That is meaningful behavioral context layered on top of readOnlyHint=false and openWorldHint=true. It doesn't explain what comes back on success (e.g., ticket URL) or what happens on Linear/Jira duplicates.

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?

Three short sentences, front-loaded with the action and destination before the constraints. Every sentence carries information (scope, body characteristics, dedup rule, write permission), with no filler, though 'connected on the Tools tab' is a slightly UI-flavored aside.

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?

For a two-parameter mutation with no output schema, it covers the write-permission prerequisite, dedup behavior, and body contents, which is the important part. It leaves the issue_id parameter undefined in both schema and prose and says nothing about the return value (ticket identifier/URL), which an agent needs to confirm success.

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 the description needs to carry parameter meaning and largely doesn't: 'issue_id' is never explained (whether it's the error issue UUID, where to obtain it), and the provider list merely repeats the enum already present in the schema. Only 'for an error issue' hints at the issue_id source.

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

Purpose5/5

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

The description pairs a specific verb ('Create a ticket') with a specific resource ('for an error issue') and enumerates the three supported destinations (GitHub Issues, Linear, Jira). It also scopes itself against neighboring write tools like create_pull_request and create_fix_pr by making clear this produces an issue/ticket, not a code change.

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

Usage Guidelines4/5

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

It gives a real precondition: 'Only works when the app allows MCP writes,' which tells the agent when the call will fail. It also states a usage constraint ('One GitHub issue per error issue'), but never names an alternative tool or says when not to file a ticket versus some other action, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources