Skip to main content
Glama

Pub Dev List Versions

pub_dev_list_versions
Read-onlyIdempotent

List all published versions of a Dart/Flutter package on pub.dev, with each version string and its publish date, plus the current latest version.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "http"
    },
    "name": "pub_dev_list_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYespub.dev package name, e.g. "http".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description does add useful return-content detail (version strings, publish dates, latest version) in the absence of an output schema, but says nothing about ordering, pagination, or behavior for a nonexistent package.

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?

A single front-loaded sentence that states the action, the resource, and the return contents with no filler. Every clause earns its place.

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 one-parameter read tool with annotations and no output schema, the description covers purpose and result shape well enough to call correctly. Minor gaps remain around ordering, result size, and error behavior for unknown package names.

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?

The single parameter has 100% schema coverage including an example value ("http"), so the schema already carries parameter meaning. The description confirms the package domain (Dart/Flutter, pub.dev) but adds no format or edge-case detail beyond the schema, matching the baseline for fully documented params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: list all published versions of a Dart/Flutter package on pub.dev. The scope (versions of one named package) is distinct from a package-detail lookup, so an agent can infer it differs from pub_dev_get_package without opening schemas, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no stated alternative, such as using pub_dev_get_package for metadata versus this tool for version history. Usage is only implied by the stated purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.