Skip to main content
Glama

List Network starter packs

list_starter_packs

Discover starter pack trackers to follow on Monity Network by category, such as restocks or price drops, each with its sources. Use it to find what you can follow about a topic.

Instructions

Starter packs: trackers picked to start from on Monity Network (restocks, price drops, AI pricing, status pages…), most followed first, each with its sources. Good for "what can I follow about X?".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many (default 12)
categoryNoOnly this topic, e.g. deals

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior beyond the schema: result ordering ('most followed first') and that each entry includes its underlying sources. It does not state that the operation is read-only/side-effect free, nor anything about auth, pagination, or what happens when category yields no packs.

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?

Front-loaded with the resource name, then a compact parenthetical of examples, then ordering, return composition, and the use case. No filler sentences. The parenthetical example list is slightly long but earns its place by making the concept concrete.

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, zero-required read tool with no output schema or annotations, the description covers what the items are, ordering, and that sources are attached — enough to call it correctly. Gaps around pagination and the semantics of an empty category result are minor at this complexity.

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%: 'limit' documents range and default (12, max 24) and 'category' gives an example ('deals'). The description adds no parameter-level detail beyond that, so the baseline 3 applies; the phrase 'about X' loosely maps to category but adds no syntax guidance.

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 ('List' + 'starter packs') and defines what the resource is: curated trackers with examples (restocks, price drops, AI pricing, status pages). It also names the ordering ('most followed first') and return shape ('each with its sources'). It stops short of explicitly contrasting with siblings like list_network_follows or search_network, so the distinction has to be inferred from the 'curated starter pack' framing.

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?

The clause 'Good for "what can I follow about X?"' gives an implied discovery use case, which is real guidance. But there are no exclusions (e.g. when to use search_network or list_network_follows instead) and no prerequisites or notes about the relationship between browsing packs and following them.

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