Skip to main content
Glama

Laraue Boards

by com.laraue
OverviewDiscussionsAdmin

create_issue

Creates a new issue in the space the given status belongs to, and returns its key. Requires canCreateIssue on that space (see list_spaces).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNoFiles to attach, base64-encoded - each becomes an attachment on the issue. Only image/jpeg, image/jpg and image/png; max 3MB each.
titleYesThe issue's title: a short one-line summary, max 256 characters. Required.
contentYesThe issue's text content, max 4096 characters.
statusIdYesThe status to create the issue in, from list_statuses - this also determines the destination space.
assigneeIdNoUser id to assign the issue to, from list_members. Must belong to the caller's organization. Omit to assign yourself.
attributesNoAttribute id -> plain-text value, e.g. {"5": "7"}. See list_attributes for ids/types/allowed values - for a List attribute, the value is one of its list value ids. Omit to leave every attribute unset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"The issue's text content."New value: +"The issue's text content, max 4096 characters."
    • addedInput schema / properties / content / maxLength
      Added value: +4096
    • addedInput schema / properties / title / maxLength
      Added value: +256
  2. Changed2 schema fields changed
    • addedInput schema / properties / title
      Added value: +{
+  "description": "The issue's title: a short one-line summary, max 256 characters. Required.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "content",
-  "statusId"
-]New value: +[
+  "content",
+  "title",
+  "statusId"
+]
  3. Changed4 schema fields changed
    • addedInput schema / properties / assigneeId
      Added value: +{
+  "default": null,
+  "description": "User id to assign the issue to, from list_members. Must belong to the caller's organization. Omit to assign yourself.",
+  "format": "uuid",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / properties / attributes / description
      Previous value: -"Attribute id -> plain-text value, e.g. {\"5\": \"7\"}. Call list_attributes first for the ids/types/expected format per attribute - for a List-typed attribute, the value is one of its list value ids (also from list_attributes), not its display text. Omit to leave every attribute unset."New value: +"Attribute id -> plain-text value, e.g. {\"5\": \"7\"}. See list_attributes for ids/types/allowed values - for a List attribute, the value is one of its list value ids. Omit to leave every attribute unset."
    • changedInput schema / properties / files / description
      Previous value: -"Files to attach, base64-encoded. Only image/jpeg, image/jpg and image/png are supported, max 3MB each."New value: +"Files to attach, base64-encoded - each becomes an attachment on the issue. Only image/jpeg, image/jpg and image/png; max 3MB each."
    • changedInput schema / properties / statusId / description
      Previous value: -"The status id to create the issue in, from list_statuses - this also determines which space the issue lands in."New value: +"The status to create the issue in, from list_statuses - this also determines the destination space."
  4. Changed5 schema fields changed
    • changedInput schema / properties / attributes / description
      Previous value: -"Attribute name -> plain-text value, e.g. {\"Priority\": \"High\"}. Call list_attributes to see what's available and the expected value format per type. Omit to leave every attribute unset."New value: +"Attribute id -> plain-text value, e.g. {\"5\": \"7\"}. Call list_attributes first for the ids/types/expected format per attribute - for a List-typed attribute, the value is one of its list value ids (also from list_attributes), not its display text. Omit to leave every attribute unset."
    • addedInput schema / properties / files
      Added value: +{
+  "default": null,
+  "description": "Files to attach, base64-encoded. Only image/jpeg, image/jpg and image/png are supported, max 3MB each.",
+  "items": {
+    "properties": {
+      "base64Content": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "contentType": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fileName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "fileName",
+      "contentType",
+      "base64Content"
+    ],
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
    • removedInput schema / properties / spaceKey
      Removed value: -{
-  "description": "The space to create the issue in, e.g. 'BRD'.",
-  "type": "string"
-}
    • changedInput schema / properties / statusId / description
      Previous value: -"The status id to create the issue in, from list_statuses - must belong to spaceKey."New value: +"The status id to create the issue in, from list_statuses - this also determines which space the issue lands in."
    • changedInput schema / required
      Previous value: -[
-  "spaceKey",
-  "content",
-  "statusId"
-]New value: +[
+  "content",
+  "statusId"
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool creates a new issue and returns its key, and that it requires canCreateIssue on the space. It does not mention side effects (e.g., notifications), whether creation is transactional, rate limits, or what happens on validation failure. This is a mutation tool, so more detail would be helpful.

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 description is two sentences, front-loaded with the core action and return value, followed by the prerequisite. Every sentence earns its place; no repetition or filler.

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 create tool with no annotations and no output schema, the description covers the essential action, return value, and a required permission. It could be slightly more complete by mentioning that files are attached, or by hinting at validation constraints already in the schema (max lengths, file types). However, the schema handles parameter details thoroughly, so this is close to complete.

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?

The schema has 100% description coverage; every parameter is fully described in the input schema. The description adds no parameter-level semantics beyond what the schema already states. Per the rules, with high schema coverage the baseline is 3.

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 uses a specific verb+resource ("Creates a new issue") and adds a scope detail: the issue is created in the space the given status belongs to, and it returns the issue key. It is clear, though it doesn't explicitly contrast with the sibling edit_issue or create_comment, so it falls short of perfect sibling differentiation.

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?

The description states the prerequisite permission (canCreateIssue) and points to list_spaces for context, which gives some usage context. However, it does not say when to use this tool versus alternatives like edit_issue, nor does it mention any exclusions or typical call flow beyond the permission note.

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

All Laraue Boards toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources