Skip to main content
Glama

Pub Dev Search Packages

pub_dev_search_packages
Read-onlyIdempotent

Search pub.dev for Dart & Flutter packages by keyword. Returns matching package names and a next-page URL.

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": {
      "query": "state management"
    },
    "name": "pub_dev_search_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1).
queryYesSearch terms, e.g. "state management" or "http client".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, and the description adds the one thing they cannot: what comes back ('matching package names and a next-page URL'), which matters because there is no output schema. It stops short of stating a result count per page or whether paging ends when the URL is absent.

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 short sentences, front-loaded with the action and resource, with the return shape in the second. No filler, no restatement of the title.

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 two-parameter, read-only search with full schema coverage and no output schema, this is nearly sufficient: parameters are documented in the schema and the return shape is in the description. The only real gap is the absence of routing guidance versus the companion package tools.

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%, and the schema itself explains both `query` and `page` with defaults and examples, so the description adds nothing beyond it. The phrase 'by keyword' restates `query` rather than clarifying syntax such as multi-word or quoted terms.

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?

States a specific verb and resource ('Search pub.dev for ... packages') plus the domain ('Dart & Flutter') and the search input ('by keyword'). What's missing is any explicit contrast with pub_dev_get_package, so an agent must infer that this is the discovery step rather than the detail-lookup step.

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?

No when-to-use guidance, no prerequisites, and no mention of when this should be preferred over fetching a specific package. Usage is only implied by the word 'search'; an agent that already knows the package name gets no signal here about whether to still call this first.

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.