Skip to main content
Glama
servelink-swyftlabs

serve

by servelink-swyftlabs
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

List links

links
Read-only

List all owned link labels with kind, URL, live/stale status, protection, activity, and quarantine window. Use this to review what is currently published or select a label for further actions.

Instructions

Inventory of every owned link (label) for the account, one record each: kind, URL, live/stale markers, protection status, last bound/viewer activity, and quarantine window. Use this to see what is currently served or published, or to find a label to act on. Live-tunnel capacity (live/max) and storage, transfer and publish-rate usage come along as context. For plan, entitlement and quota headroom, use account_status instead. Owned links are unlimited by count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
countYes
linksYes
publishNo
storageNo
transferNo
max_tunnelsYes
live_tunnelsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.8
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "links": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "artifact_kind": {
+            "type": "string"
+          },
+          "credential_state": {
+            "type": "string"
+          },
+          "expires_at": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "last_bound_at": {
+            "type": "string"
+          },
+          "last_viewer_at": {
+            "type": "string"
+          },
+          "live": {
+            "type": "boolean"
+          },
+          "protected": {
+            "type": "boolean"
+          },
+          "protection_version": {
+            "type": "integer"
+          },
+          "published_at": {
+            "type": "string"
+          },
+          "quarantine_until": {
+            "type": "string"
+          },
+          "residency": {
+            "type": "string"
+          },
+          "size_bytes": {
+            "type": "integer"
+          },
+          "stale": {
+            "type": "boolean"
+          },
+          "ttl_hours": {
+            "type": [
+              "null",
+              "integer"
+            ]
+          },
+          "url": {
+            "type": "string"
+          },
+          "version": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "label",
+          "kind",
+          "url",
+          "live",
+          "residency",
+          "stale",
+          "protected"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "live_tunnels": {
+      "type": "integer"
+    },
+    "max_tunnels": {
+      "type": "integer"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "publish": {
+      "additionalProperties": false,
+      "properties": {
+        "day_limit": {
+          "type": "integer"
+        },
+        "day_used": {
+          "type": "integer"
+        },
+        "hour_limit": {
+          "type": "integer"
+        },
+        "hour_used": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "hour_used",
+        "hour_limit",
+        "day_used",
+        "day_limit"
+      ],
+      "type": "object"
+    },
+    "storage": {
+      "additionalProperties": false,
+      "properties": {
+        "limit_bytes": {
+          "type": "integer"
+        },
+        "used_bytes": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "used_bytes",
+        "limit_bytes"
+      ],
+      "type": "object"
+    },
+    "transfer": {
+      "additionalProperties": false,
+      "properties": {
+        "limit_bytes": {
+          "type": "integer"
+        },
+        "reset_at": {
+          "type": "string"
+        },
+        "used_bytes": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "used_bytes",
+        "limit_bytes"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "ok",
+    "links",
+    "count",
+    "live_tunnels",
+    "max_tunnels"
+  ],
+  "type": "object"
+}
  2. First observedv0.8.6

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with those. It adds useful behavioral context beyond the annotations: the output is one record per owned link, includes live/stale/protection/activity/quarantine fields, and carries live-tunnel capacity and usage as context. The note that owned links are unlimited by count is also helpful. It does not describe pagination or rate-limit behavior, but annotations already cover the safety profile.

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?

Four sentences, each earning its place: the first defines the inventory and record contents, the second gives usage intent, the third notes companion context data, and the fourth routes to a sibling and clarifies count limits. The key content is front-loaded, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only list tool with an output schema present, the description is complete. It gives purpose, scope, record categories, companion usage context, an explicit alternative, and a count-limit clarification. Nothing an agent needs to select or call this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters in the input schema, so the baseline is 4. The description does not need to explain parameter meaning because there is nothing to explain. It focuses instead on what the returned inventory contains, which is appropriate for a zero-parameter read-only list.

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 states a specific verb-resource relationship: it inventories every owned link for the account, enumerates record contents (kind, URL, live/stale markers, protection status, activity, quarantine window), and clarifies what the tool is for (seeing what is served/published or finding a label to act on). It also distinguishes itself from account_status by explicitly routing quota/plan questions elsewhere.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit use cases: 'Use this to see what is currently served or published, or to find a label to act on.' It also names the alternative for plan/entitlement/quota questions: 'use account_status instead.' This provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/servelink-swyftlabs/serve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server