Skip to main content
Glama

Black Friday AI deals

list_deals
Read-only

Black Friday 2026 deals on AI tools, each one opened and checked by a person: the deal, its price, code and end time, and what a year costs against paying yearly on a normal day. Live and coming deals, the soonest ending first. Paid top spots are marked sponsored.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly deals in this category

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value beyond that by disclosing human verification of each deal, the fields returned (price, code, end time, annual-cost comparison), the sort order, and that paid placements are marked sponsored. It omits pagination, result-count limits, and rate behavior, so it is strong but not exhaustive.

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?

The content is packed into one front-loaded sentence with a colon-delimited field list, which is efficient and readable. It is dense but every clause (verification, fields, sort order, sponsored disclosure) carries information the agent needs.

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 read-only list tool with one optional enum parameter and no output schema, the description covers what the entries contain, how they are ordered, and the sponsorship disclosure. Remaining gaps — pagination, total result limits, and how the category filter interacts with the listing — are minor.

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?

There is a single optional parameter, category, and schema description coverage is 100% with a full enum, so the schema already carries the semantics. The description adds nothing about the category filter, so the baseline of 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 resource precisely (Black Friday 2026 deals on AI tools) and describes what each entry carries, so an agent knows this is a curated deals listing. It does not explicitly distinguish itself from siblings such as list_upcoming or list_categories, which keeps it below a 5.

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?

Usage is implied rather than stated: 'Live and coming deals, the soonest ending first' tells the agent this covers both current and upcoming offers, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that list_upcoming or list_categories serve narrower purposes.

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