Skip to main content
Glama
Sign In

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

NameRequiredDescriptionDefault
filesNoFiles to attach, base64-encoded - each becomes an attachment on the issue. The type is recognized from the content, not contentType: images JPEG, PNG, WebP, GIF (max 3MB each) or documents PDF, DOCX, DOC, and UTF-8 text by fileName's extension - .md, .txt, .json (max 10MB each). SVG, HEIC and others are rejected.
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. Changed1 schema field changed
    • changedInput schema / properties / files / description
      Previous value: -"Files to attach, base64-encoded - each becomes an attachment on the issue. Only image/jpeg, image/jpg and image/png; max 3MB each."New value: +"Files to attach, base64-encoded - each becomes an attachment on the issue. The type is recognized from the content, not contentType: images JPEG, PNG, WebP, GIF (max 3MB each) or documents PDF, DOCX, DOC, and UTF-8 text by fileName's extension - .md, .txt, .json (max 10MB each). SVG, HEIC and others are rejected."
  2. 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
  3. 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"
+]
  4. 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."
  5. 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"
+]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the load and does add real behavior: the permission gate, the implicit space resolution from statusId, and the fact that a key is returned. It omits side effects such as notifications, attachment processing, or failure modes for a missing/invalid status, which is the remaining gap for an unannotated mutation tool.

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?

Two sentences, zero filler, with the core action and scope stated first and the permission requirement second. Nothing could be removed without losing information.

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?

With dense schema descriptions and no output schema, the description covers the essentials an agent needs: permission, space resolution, and the returned key. It stops short of describing error behavior or side effects, which for a creation tool leaves a small but real gap.

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 every parameter including files, assigneeId, and attributes is already documented in detail. The description adds no parameter-level meaning beyond what the schema states; its space-derivation note merely echoes the statusId description. Baseline 3 applies.

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?

States a specific verb and resource ('Creates a new issue'), plus a non-obvious scoping rule: the destination space is derived from the given status. It also declares the return value ('its key'), so an agent can distinguish it from edit_issue, create_issue_link, or create_comment without opening any schema.

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?

Gives an explicit prerequisite ('Requires canCreateIssue on that space') and routes the agent to list_spaces for verification. It does not spell out when to prefer this over edit_issue or how to obtain a statusId beyond the schema's own pointer to list_statuses, so no exclusion guidance is present.

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