Skip to main content
Glama

Coline

Create an issue

create_upstream_issue

Opens an issue in a repository on Upstream as the person, optionally with labels and assignees.

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": {
      "workspace": "<workspace>",
      "repository": "<repository>",
      "title": "<title>"
    },
    "name": "create_upstream_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
titleYes
labelsNoLabel names that exist in the repository.
assigneesNoHandles of people who can be assigned.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
stateYes
titleYes
authorYes
labelsYes
numberYes
commentsYes
assigneesYes
updatedAtYes
resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the issue is created "as the person," i.e. under the authenticated identity — but says nothing about failure modes, permission requirements, or what happens with invalid labels.

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 filler; the optional extras are correctly subordinated with "optionally." Slightly terse given how little it says about the required fields.

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?

An output schema exists, so return values need no explanation, and the write is non-destructive. However, for a six-parameter create tool it omits that workspace, repository, and title are mandatory and where those values come from, leaving the agent to rely entirely on the schema.

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 coverage is 67%, with labels and assignees already documented in the schema; the description merely echoes them as optional. The undocumented parameters (title, body) get no added meaning from the description, so it does not compensate for the coverage gap beyond the baseline.

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 gives a specific verb and resource ("Opens an issue") plus the target system ("a repository on Upstream"), which separates it cleanly from read/comment/update siblings. It stops short of explicitly naming an alternative tool, so it is clear but not sibling-differentiating in the strongest sense.

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 guidance on when to create an issue versus commenting on an existing one or updating one, and no prerequisites (such as needing a valid workspace/repository or pre-existing labels) are stated. Usage is only implied by the verb.

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