Skip to main content
Glama

Pub Dev Get Package

pub_dev_get_package
Read-onlyIdempotent

Get metadata for a Dart/Flutter package on pub.dev: latest version, description, homepage, repository, supported SDK environment, and publish date (from the pubspec).

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_get_package"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the safety profile is fully covered by structured data. The description adds real value by disclosing the return payload's contents and that the data is drawn from the pubspec, which matters given there is no output schema. It says nothing about behavior for nonexistent packages, staleness, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with a clear verb phrase followed by an enumerated field list; every clause carries information. The repeated title/name phrasing in the opening is the only minor redundancy.

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 single-parameter read-only lookup with no output schema, the description compensates by naming the returned fields, which is the key missing structured information. It is not fully complete on error/edge behavior (unknown package names, prerelease versions), but nothing critical to a correct invocation is absent.

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 "name" parameter documented and exampled ("http", "provider"). The description adds no meaning beyond that (no format constraints, no scoped-package handling such as "@scope/name"), so the baseline 3 applies.

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 ("Get metadata for a Dart/Flutter package on pub.dev") and enumerates exactly which fields are returned (latest version, description, homepage, repository, SDK environment, publish date). This distinguishes it reasonably well from likely siblings such as get_package_score and pub_dev_list_versions, though those siblings are never 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is for looking up a known package by name. There is no explicit statement of when to use this versus pub_dev_list_versions (version history) or pub_dev_search_packages (discovery when the name is unknown), and no exclusion guidance is given.

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.