Skip to main content
Glama
zzstoatzz

Tangled MCP Server

by zzstoatzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_repo_issue

Create a repository issue on Tangled by specifying the owner/repo, title, and optional body or labels. Returns a clickable URL and issue ID.

Instructions

create an issue on a repository

Args: repo: repository identifier in 'owner/repo' format title: issue title body: optional issue body/description labels: optional list of label names to apply

Returns: CreateIssueResult with url (clickable link) and issue_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesrepository identifier in 'owner/repo' format (e.g., 'zzstoatzz/tangled-mcp')
titleYesissue title
bodyNo
labelsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlYesconstruct clickable tangled.org URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.0.12
    • addedOutput schema / properties / id
      Added value: +{
+  "type": "integer"
+}
    • removedOutput schema / properties / issue_id
      Removed value: -{
-  "type": "integer"
-}
    • removedOutput schema / properties / repo
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "repo",
-  "issue_id",
-  "url"
-]New value: +[
+  "id",
+  "url"
+]
  2. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / labels
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "optional list of label names (e.g., ['good-first-issue', 'bug']) to apply to the issue"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedOutput schema / additionalProperties
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / description
      Added value: +"result of creating an issue"
    • addedOutput schema / properties
      Added value: +{
+  "issue_id": {
+    "type": "integer"
+  },
+  "repo": {
+    "type": "string"
+  },
+  "url": {
+    "description": "construct clickable tangled.org URL",
+    "readOnly": true,
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "repo",
+  "issue_id",
+  "url"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It reveals it creates an issue and returns a URL and issue ID, but does not disclose side effects, permissions, or rate limits. It is adequate but not richly transparent.

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?

The description is concise with a clear purpose statement followed by an Args list and Returns. It is front-loaded with the main action. A slightly more structured format or removal of repetitive schema info could make it more efficient.

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?

Covers the main purpose, required parameters, and return values. However, it lacks context on error handling, authentication, prerequisites, and how the tool fits with siblings. For a creation tool, this is sufficient but not comprehensive.

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 50%, so the description should compensate. It repeats the schema's parameter descriptions (e.g., repo format, optional body/labels) without adding significant new meaning or usage context beyond what is already in the schema.

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 clearly states 'create an issue on a repository,' which is a specific verb+resource. It distinguishes from siblings like delete_repo_issue, list_repo_issues, and update_repo_issue by focusing on creation.

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?

No explicit guidance on when to use or when not to use this tool versus alternatives. The purpose is implied by the name and description, but there are no exclusions or context-specific recommendations.

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

Deploy Server

Other Tools