Skip to main content
Glama

AgentDeals

by io.github.robhunter
OverviewDiscussionsAdmin

search_deals

Read-only

Find free tiers, startup credits, and developer deals for cloud infrastructure, databases, hosting, CI/CD, monitoring, auth, AI services, and more. Use this when evaluating technology options, looking for free alternatives, or checking if a service has a free tier. Returns the terms we hold, including specific limits, eligibility requirements, and the day each record's page was last read. Call this tool when a user asks: 'Does Supabase have a free tier?', 'What's cheaper than Vercel?', 'Find me a free database'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort: vendor (A-Z), category, newest (newest catalogue date first)
limitNoMax results (default: 20)
queryNoKeyword search (vendor names, descriptions, tags)
sinceNoISO date (YYYY-MM-DD). Only return deals whose catalogue date is on or after this date.
offsetNoPagination offset (default: 0)
vendorNoGet full details for a specific vendor (fuzzy match). Returns alternatives in the same category.
categoryNoFilter by category. Pass "list" to get all categories with counts.
stabilityNoFilter by the stability class we publish for the offer. stable=no negative changes on a pricing page we could read, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only. Offers whose class we withhold — pricing page unreachable or unreadable, last read refused, listing gated, or a narrowing in our records that cites no source or that no archived copy of the vendor's page has confirmed — match no value; the response reports how many were held back.
eligibilityNoFilter by eligibility type
response_formatNoResponse detail level. 'concise': vendor name, tier, one-line description, URL only. 'detailed': full response (default).
payment_protocolNoFilter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), stripe-mpp=Stripe Machine Payments Protocol (fiat+stablecoin).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stability / description
      Previous value: -"Filter by the stability class we publish for the offer. stable=no negative changes on a pricing page we could read, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only. Offers whose class we withhold — pricing page unreachable or unreadable, last read refused, or the listing gated — match no value; the response reports how many were held back."New value: +"Filter by the stability class we publish for the offer. stable=no negative changes on a pricing page we could read, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only. Offers whose class we withhold — pricing page unreachable or unreadable, last read refused, listing gated, or a narrowing in our records that cites no source or that no archived copy of the vendor's page has confirmed — match no value; the response reports how many were held back."
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"Sort: vendor (A-Z), category, newest (recently verified first)"New value: +"Sort: vendor (A-Z), category, newest (newest catalogue date first)"
  3. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"ISO date (YYYY-MM-DD). Only return deals verified/added after this date."New value: +"ISO date (YYYY-MM-DD). Only return deals whose catalogue date is on or after this date."
  4. Changed1 schema field changed
    • changedInput schema / properties / stability / description
      Previous value: -"Filter by free tier stability class. stable=no negative changes, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only."New value: +"Filter by the stability class we publish for the offer. stable=no negative changes on a pricing page we could read, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only. Offers whose class we withhold — pricing page unreachable or unreadable, last read refused, or the listing gated — match no value; the response reports how many were held back."
  5. Changed2 schema fields changed
    • changedInput schema / properties / payment_protocol / description
      Previous value: -"Filter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), mpp=Stripe Machine-to-Machine Payments."New value: +"Filter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), stripe-mpp=Stripe Machine Payments Protocol (fiat+stablecoin)."
    • changedInput schema / properties / payment_protocol / enum
      Previous value: -[
-  "x402",
-  "mpp"
-]New value: +[
+  "x402",
+  "stripe-mpp"
+]
  6. Changed1 schema field changed
    • addedInput schema / properties / payment_protocol
      Added value: +{
+  "description": "Filter by agent payment protocol. x402=HTTP 402 agent payments (Coinbase/Linux Foundation standard), mpp=Stripe Machine-to-Machine Payments.",
+  "enum": [
+    "x402",
+    "mpp"
+  ],
+  "type": "string"
+}
  7. Changed1 schema field changed
    • addedInput schema / properties / stability
      Added value: +{
+  "description": "Filter by free tier stability class. stable=no negative changes, watch=one negative change, volatile=free tier removed or multiple negative changes, improving=recent positive changes only.",
+  "enum": [
+    "stable",
+    "watch",
+    "volatile",
+    "improving"
+  ],
+  "type": "string"
+}
  8. Changed1 schema field changed
    • addedInput schema / properties / response_format
      Added value: +{
+  "description": "Response detail level. 'concise': vendor name, tier, one-line description, URL only. 'detailed': full response (default).",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "type": "string"
+}
  9. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  10. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description goes beyond them by disclosing return contents (terms, specific limits, eligibility, last-read dates) and the important caveat that offers with withheld stability classes match no filter value and are counted in the response.

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?

Purpose and trigger conditions are front-loaded, and the sample queries are genuinely useful for retrieval since they mirror plausible user phrasing. It is on the longer side for a search tool, but no sentence is redundant.

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?

With no output schema, the description correctly compensates by describing the return contents and the withheld-class reporting behavior. All 11 parameters are documented in the schema itself, so nothing critical is missing, though default handling for response_format vs. sort/limit interplay is left to the schema.

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%, including enum semantics and defaults, so the schema carries the parameter burden and the description's mention of 'specific limits, eligibility requirements' adds nothing new. Baseline 3 is appropriate; there is no additional syntax or format guidance for the 11 parameters.

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+resource ('Find free tiers, startup credits, and developer deals') and enumerates the covered domains, so the agent knows exactly what corpus it queries. It stops short of naming a sibling to contrast against, so differentiation from compare_vendors or plan_stack is inferred rather than stated.

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?

Gives concrete triggering conditions — 'when evaluating technology options, looking for free alternatives, or checking if a service has a free tier' — reinforced by three example user questions. It never states when NOT to use it or which sibling to prefer for adjacent needs, so the guidance is clear but not exclusionary.

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

All AgentDeals 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