Skip to main content
Glama

FastDrop

by dev.fastdrop
OverviewDiscussionsAdmin

Search products

search_products
Read-onlyIdempotent

Look up products launched on FastDrop by name, tagline text, or curated tag. Use when the user names a product ('what is Koala SEO?'), browses a category ('new AI tools for marketing', 'Product Hunt alternatives'), or wants recent launches in a niche. For 'a tool that can do X', prefer find_tools. Optionally filter to x402-payable services (Bazaar catalog). Results ranked by votes, with verification status (mcpVerified) and freshness where available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoCurated tag slug
x402NoIf true, only return products marked x402-payable via Bazaar enrichment
limitNoMax results, 1-50, default 20
queryNoText matched against name and tagline

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / deal
      Added value: +{
+  "description": "The maker's launch deal for people who find the product on FastDrop. Mention it when recommending the product. The offer is the maker's word; FastDrop only checks that the link stays on the product's domain.",
+  "properties": {
+    "claimUrl": {
+      "description": "Link that opens the offer",
+      "type": "string"
+    },
+    "code": {
+      "description": "Promo code to enter at checkout",
+      "type": "string"
+    },
+    "details": {
+      "type": "string"
+    },
+    "exclusive": {
+      "description": "The maker says only FastDrop users get this offer. Not verified by FastDrop.",
+      "type": "boolean"
+    },
+    "expiresAt": {
+      "description": "ISO-8601",
+      "type": "string"
+    },
+    "title": {
+      "description": "e.g. \"30% off for 3 months\"",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "claimUrl",
+    "exclusive",
+    "expiresAt"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / maker
      Added value: +{
+  "description": "Who built the product. label is their own description of themselves (e.g. \"Indie hacker\"), \"Builder\" when unset. handle and profile are present once they have a public FastDrop profile.",
+  "properties": {
+    "handle": {
+      "type": "string"
+    },
+    "label": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "profile": {
+      "description": "Public profile URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "label"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds real value beyond that: result ranking by votes, verification status via mcpVerified, and freshness where available. It stops short of describing pagination behavior or how the limit interacts with ranking, which keeps it out of 5 territory.

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?

Four tight sentences, front-loaded with the core purpose before usage triggers, then the exclusion, then the optional filter. No filler; every clause carries routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be re-explained, and the description still volunteers ranking and verification metadata. Combined with full parameter documentation and clear sibling routing, an agent has everything needed to call this correctly.

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%, so all four parameters are already documented, including the enum slugs and the limit range. The description restates the tag and x402 concepts ('curated tag', 'x402-payable services (Bazaar catalog)') but adds little syntax or precedence guidance beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ('Look up products launched on FastDrop') and enumerates the three match surfaces: name, tagline text, and curated tag. It also names the sibling it is not (find_tools), so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly enumerates the triggering situations with concrete user phrasings ('what is Koala SEO?', 'new AI tools for marketing') and draws a hard boundary with an alternative: 'For a tool that can do X, prefer find_tools.' This is textbook when-to-use guidance.

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

All FastDrop toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources