Skip to main content
Glama
zzstoatzz

Tangled MCP Server

by zzstoatzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_repo_issues

List issues for a Tangled repository by specifying the owner/repo identifier. Optionally set the maximum number of issues to return (1-100).

Instructions

list issues for a repository

Args: repo: repository identifier in 'owner/repo' format limit: maximum number of issues to return (1-100)

Returns: ListIssuesResult with list of issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesrepository identifier in 'owner/repo' format (e.g., 'zzstoatzz/tangled-mcp')
limitNomaximum number of issues to return

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
issuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.0
    • removedInput schema / properties / cursor
      Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "pagination cursor"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +20
    • addedOutput schema / $defs
      Added value: +{
+  "IssueInfo": {
+    "description": "issue information",
+    "properties": {
+      "body": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "cid": {
+        "type": "string"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "issueId": {
+        "type": "integer"
+      },
+      "labels": {
+        "default": [],
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "title": {
+        "type": "string"
+      },
+      "uri": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "uri",
+      "cid",
+      "issueId",
+      "title",
+      "createdAt"
+    ],
+    "type": "object"
+  }
+}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / description
      Added value: +"result of listing issues"
    • addedOutput schema / properties
      Added value: +{
+  "issues": {
+    "items": {
+      "$ref": "#/$defs/IssueInfo"
+    },
+    "type": "array"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "issues"
+]
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states that it lists issues, without mentioning read-only nature, authentication needs, rate limits, or any ordering. The output schema exists but the description does not add behavioral context beyond the action.

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 and uses a clear structure (Args, Returns). It is front-loaded with the main action. Only slightly impacted by using Python docstring style which may not be universal.

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 simple list tool with an output schema, the description covers the essential parameters and purpose. It does not mention default ordering or filtering (e.g., state), but the schema limits scope. Completeness is adequate given the tool's simplicity.

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 100%, so the input schema already documents both parameters (repo, limit). The description adds a format hint for repo but otherwise repeats schema info. It does not significantly enhance understanding beyond what the schema provides.

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 'list issues for a repository', providing a specific verb and resource. It distinguishes itself from sibling tools (create, delete, update) and other list tools (branches, labels, pulls).

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 does not explicitly guide when to use this tool versus alternatives. While the purpose is implied, there is no mention of when not to use it or comparison with sibling tools. Usage is clear from context but lacks explicit guidance.

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