Skip to main content
Glama

Crates

by io.github.pipeworx-io

Get Versions

get_versions
Read-onlyIdempotent

List all published versions for a crate in reverse chronological order. Returns version number, download count, and publish date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCrate name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
crateYesCrate name
versionsYes

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: +[
+  {
+    "name": "serde"
+  },
+  {
+    "name": "tokio"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "crate": {
+      "description": "Crate name",
+      "type": "string"
+    },
+    "versions": {
+      "items": {
+        "properties": {
+          "downloads": {
+            "description": "Download count for this version",
+            "type": "number"
+          },
+          "license": {
+            "description": "License identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "published_at": {
+            "description": "Publication timestamp",
+            "type": "string"
+          },
+          "rust_version": {
+            "description": "Minimum Rust version required",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "version": {
+            "description": "Version number",
+            "type": "string"
+          },
+          "yanked": {
+            "description": "Whether version is yanked",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "version",
+          "downloads",
+          "published_at",
+          "yanked",
+          "license",
+          "rust_version"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "crate",
+    "versions"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "name": "serde"
-  },
-  {
-    "name": "tokio"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "crate": {
-      "description": "Crate name",
-      "type": "string"
-    },
-    "versions": {
-      "items": {
-        "properties": {
-          "downloads": {
-            "description": "Download count for this version",
-            "type": "number"
-          },
-          "license": {
-            "description": "License identifier",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "published_at": {
-            "description": "Publication timestamp",
-            "type": "string"
-          },
-          "rust_version": {
-            "description": "Minimum Rust version required",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "version": {
-            "description": "Version number",
-            "type": "string"
-          },
-          "yanked": {
-            "description": "Whether version is yanked",
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "version",
-          "downloads",
-          "published_at",
-          "yanked",
-          "license",
-          "rust_version"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "crate",
-    "versions"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "crate": {
+      "description": "Crate name",
+      "type": "string"
+    },
+    "versions": {
+      "items": {
+        "properties": {
+          "downloads": {
+            "description": "Download count for this version",
+            "type": "number"
+          },
+          "license": {
+            "description": "License identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "published_at": {
+            "description": "Publication timestamp",
+            "type": "string"
+          },
+          "rust_version": {
+            "description": "Minimum Rust version required",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "version": {
+            "description": "Version number",
+            "type": "string"
+          },
+          "yanked": {
+            "description": "Whether version is yanked",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "version",
+          "downloads",
+          "published_at",
+          "yanked",
+          "license",
+          "rust_version"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "crate",
+    "versions"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "serde"
+  },
+  {
+    "name": "tokio"
+  }
+]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds that the tool returns data in reverse chronological order, which is useful but not critical 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?

The description is a single efficient sentence that conveys purpose and output. It contains no redundant phrases or unnecessary details.

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 simple tool (one required param, list operation) and presence of an output schema, the description covers purpose, input, and output adequately. It lacks mention of error conditions or limits, but these are minor omissions for a straightforward tool.

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% with a single required parameter 'name' described as 'Crate name'. The description does not add any additional parameter details, so it meets the baseline for high coverage but provides no extra value.

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 the tool lists published versions for a crate in reverse chronological order, specifying the output fields (version number, download count, publish date). It distinguishes itself from sibling tools like get_crate or search_crates by focusing on versions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as get_crate or search_crates. It lacks context about prerequisites or scenarios where this tool is preferred.

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

All Crates 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

A4/5.0
Disambiguation3/5

The tool set includes several overlapping research/lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and multiple Polymarket tools, which could confuse an agent despite detailed descriptions. The boundaries between these tools are explained in the descriptions, but the sheer number of similar-purpose tools creates ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., search_crates, get_versions, validate_claim), but there are exceptions like entity_profile, deep_research, and bet_research, which break the pattern. The overall naming is readable and mostly consistent, with the polymarket_ and pipeworx_ prefixes providing grouping.

Tool Count2/5

With 35 tools, the server is far too heavy for a focused service. The server name 'Crates' suggests a narrow domain, but only 5 tools relate to Rust crates, while the rest cover disparate areas (Pipeworx, Polymarket, memory management). This mismatch and high count make the tool surface unwieldy.

Completeness4/5

For the underlying Pipeworx/Polymarket domain that the majority of tools serve, the coverage is strong: lookup, grounded answers, research, entity profiles, comparisons, changes, claim validation, scanning, memory, subscriptions, tool discovery. Minor gaps exist (e.g., no direct summarization), but the set feels well-rounded for a data analysis agent.

Resources