Skip to main content
Glama

Pkg Go Dev

by io.github.pipeworx-io

List Versions

list_versions
Read-onlyIdempotent

List all published versions of a Go module by its import path (e.g. "github.com/gin-gonic/gin") from proxy.golang.org. Returns a sorted array of semver version strings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_pathYesModule import path (e.g. "github.com/gin-gonic/gin", "golang.org/x/net")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of published versions
versionsYesList of published versions, sorted
module_pathYesModule import path

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "module_path": "github.com/gin-gonic/gin"
+  },
+  {
+    "module_path": "golang.org/x/net"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of published versions",
+      "type": "integer"
+    },
+    "module_path": {
+      "description": "Module import path",
+      "type": "string"
+    },
+    "versions": {
+      "description": "List of published versions, sorted",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "module_path",
+    "count",
+    "versions"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds that it fetches from proxy.golang.org (external source) and returns sorted semver strings, which are behavioral details beyond annotations.

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, first sentence states action and parameter, second sentence states output format. No unnecessary words.

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?

Given the tool's simplicity and the presence of output schema, the description covers core functionality. Could mention error handling but not essential.

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% for the single parameter, and the description reiterates the parameter's purpose but does not add substantial new meaning beyond the schema examples. Baseline of 3 is appropriate.

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 explicitly states it lists all published versions of a Go module by import path from proxy.golang.org, and returns sorted semver strings. This clearly differentiates it from siblings like latest_version and get_module_info.

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?

While not explicitly stating when not to use, it clearly describes the tool's scope. An agent can deduce to use this for all versions, and use latest_version for the latest only.

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

All Pkg Go Dev toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all performing similar data lookups. Additionally, many tools focus on prediction markets and arbitrage, which are unrelated to the server's implied Go development domain, causing confusion.

Naming Consistency2/5

Tool names follow inconsistent conventions: some use snake_case (e.g., 'latest_version', 'list_versions'), some use underscores in longer names (e.g., 'ai_visibility_check', 'ask_pipeworx_grounded'), and some use colons in descriptions but not in names. This mix reduces predictability.

Tool Count2/5

With 35 tools, the count is high for a server named 'Pkg Go Dev' that only offers a few Go module-related tools (e.g., get_go_mod, list_versions). The majority are unrelated Pipeworx tools, making the scope mismatched and excessive.

Completeness1/5

The tool set severely lacks coverage for Go development tasks. It only includes basic module lookup tools (version listing, mod retrieval) but misses essential operations like dependency analysis, build commands, or testing. The vast majority of tools cover unrelated domains (prediction markets, company profiles, etc.), leaving the server incomplete for its intended purpose.

Resources