Skip to main content
Glama

Find deals

find_deals
Read-onlyIdempotent

Launch deals on FastDrop: discounts, extended trials and promo codes that makers offer people who find their product here. Use when the user hunts for a deal, discount, coupon or promo code on an AI tool, app or MCP server. Each product's deal has the offer, an optional code, and a claimUrl. exclusive is the maker's claim, not verified - say so if you mention it. Deals never affect rank.

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": "find_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOptional curated tag slug
limitNoMax results, 1-50, default 20
queryNoOptional text matched against name and tagline

Output Schema

NameRequiredDescriptionDefault
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / products / items / properties / domainVerified
      Added value: +{
      +  "description": "True when the maker proved they control the product URL domain by publishing a _fastdrop TXT record (the DOMAIN VERIFIED badge on the website). Independent of mcpVerified.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world lookup, so the safety bar is low. The description still adds real context beyond them: each deal carries an offer, optional code and claimUrl, 'exclusive' is an unverified maker claim that must be caveated, and deals never influence ranking.

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?

Four short sentences, front-loaded with what the tool returns, then the usage trigger, then the trust caveats. The opening verb 'Launch deals' is slightly awkward for a read operation, but no sentence is padding.

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 shape needs no explanation, and annotations cover the safety profile. The description closes the remaining gaps an agent needs: what a deal contains, that codes may be absent, and how to frame unverified 'exclusive' claims.

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 only three params (tag enum, limit, query), so the schema fully documents them; baseline 3 applies. The description adds no filtering syntax, default, or matching behavior beyond what the schema states.

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 a specific resource (deals: discounts, extended trials, promo codes) offered by makers on FastDrop, and the second sentence scopes it to AI tools, apps and MCP servers. An agent can distinguish this from search_products or find_tools, though no sibling is 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 Guidelines4/5

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

It gives a clear trigger condition: 'use when the user hunts for a deal, discount, coupon or promo code on an AI tool, app or MCP server.' There is no explicit when-not guidance or pointer to an alternative sibling for the non-deal case, which keeps it below a 5.

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.

Resources