Skip to main content
Glama
Sign In

devstack-mcp

by io.github.IsaiahDupree
OverviewDiscussionsAdmin

Get published versions / tags

get_versions
Read-onlyIdempotent

List published versions (npm/PyPI), image tags (Docker Hub, most recent 25), or extension versions (VS Code) for a package. registry=all is NOT supported here — pick a single registry. Each item carries version and released, plus registry-specific extras (files for PyPI, size for Docker tags).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "registry": "<registry>",
      "name": "<name>"
    },
    "name": "get_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name / id (scoped npm ids, Docker namespaces, and VS Code publisher.extension ids supported).
registryYesTarget registry. "all" is not supported here — pick one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 read-only, idempotent, and non-destructive behavior. The description adds useful behavioral constraints such as 'registry=all is NOT supported here' and mentions the 25-tag limit for Docker Hub, plus registry-specific extras in the output, which goes 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 two sentences, front-loaded with the main action, then a critical constraint, and finally a summary of output contents. Every sentence earns its place with no redundancy or fluff.

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?

With two parameters and no output schema, the description provides a solid overview: supported registries, the 'all' limitation, and what each item contains. It could be more explicit about pagination for non-Docker registries, but for a simple list tool, it covers the essential usage context.

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% with descriptive fields for both 'name' and 'registry'. The description adds minimal new parameter-level information, mostly reinforcing that a single registry must be chosen, which is already implied by the enum. The output details (extras) are more about return values than parameters.

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 npm/PyPI, image tags for Docker Hub, and extension versions for VS Code. It distinguishes itself from sibling tools by focusing specifically on version/tag enumeration, and even clarifies that 'registry=all' is not supported, making the purpose unambiguous.

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?

The description provides clear context on when to use the tool (list versions/tags for a package) and explicitly instructs to pick a single registry. However, it does not explicitly contrast with alternatives like get_package or get_downloads, so it lacks a full '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.

All devstack-mcp toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources