Skip to main content
Glama

Dripod

List Dripod products

list_products
Read-onlyIdempotent

The print-on-demand products Dripod can put a design on (T-shirts, hoodies, mugs, tumblers, hats, totes, phone cases, pillows, socks…), each with its blank colours and its page on drint.io. Narrow it by shelf or by a word in the name.

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

Input Schema

NameRequiredDescriptionDefault
shelfNoOnly this shelf.
searchNoOnly products whose name has this word, like "hoodie" or "mug".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the shape of each result (blank colours plus a page URL on drint.io), which matters because no output schema exists. It stops short of stating pagination, result limits, or whether the full catalog is returned.

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 compact passage that front-loads the resource definition and reserves the trailing clause for the filtering hint. The long parenthetical product enumeration is borderline padding but does usefully convey catalog breadth; nothing else is wasteful.

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-optional-parameter list tool with full schema coverage and complete annotations, the definition covers what the resources are, what each result contains, and how to narrow the set. The remaining gap is behavioral scale — no mention of result volume or paging — which is minor here because no output schema exists to conflict with.

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%: both parameters are documented and the shelf enum values are self-describing. The description's 'narrow it by shelf or by a word in the name' reinforces the schema but adds no semantics the schema lacks, 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 names the specific resource — the print-on-demand products Dripod can decorate — and enumerates concrete examples (T-shirts, mugs, tumblers, phone cases), plus states what each entry carries (blank colours and a drint.io page). It is clear what a caller gets back, though the verb 'list' is only implied and the sibling pod_mockup is never contrasted.

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?

'Narrow it by shelf or by a word in the name' tells the agent how to filter, which is real usage guidance. However, there is no statement of when to reach for this tool versus pod_mockup, no prerequisite or ordering advice, and no note on what an unfiltered call returns.

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.