Skip to main content
Glama

dealpulse

Discover the best deals, compare prices across retailers, find coupons, optimize cashback and credit card rewards, audit subscriptions for savings, and analyze price history to determine the best time to buy.

Instructions

DealPulse: Global deal intelligence API. AI-synthesized best deals, price history, coupon discovery, cashback optimization, subscription audits, credit card stack analysis, grocery savings, student discounts, an

Coverage: Global

Endpoints: • store ($0.10): Store coupon codes and promotions • item ($0.10): Best deal on a specific product • compare ($0.10): Live price comparison across retailers • event ($0.10): Sale event intelligence • subscriptions ($0.10): Subscription audit — cancel vs. keep analysis with cost savings • cards ($0.10): Credit card cashback optimization for a purchase or category • stack ($0.10): Deal stacking — combine sale + coupon + cashback for maximum savings • student ($0.10): Student discounts on software, services, food, and travel • history ($0.10): Price history and best-time-to-buy analysis for a product

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: store | item | compare | event | subscriptions | cards | stack | student | history
langNolang
storeNoStore or restaurant name (e.g. Target, Chilis, Nike)
queryNoProduct name or description (e.g. 65 inch TV, AirPods Pro)
budgetNoMaximum budget in USD
itemNoSpecific product name (e.g. Samsung 65 inch QN90B, Dyson V15)
eventNoSale event name (e.g. black-friday, prime-day, cyber-monday)
categoryNoProduct category filter (e.g. electronics, appliances, clothing)
servicesNoservices
retailerNoretailer
countryNocountry
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as rate limits, authentication, error handling, or data freshness. It only mentions cost per endpoint ($0.10) which is partial transparency.

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 description is structured with a header, coverage, and bulleted list of endpoints. It is relatively concise given the number of endpoints, though the list is lengthy. The main purpose is front-loaded.

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

Completeness3/5

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

The description covers the main endpoints but lacks details on output format, error handling, and usage examples. With no output schema and 11 parameters, it is adequate but not deeply informative. Missing behavioral context reduces completeness.

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 coverage is 100% with parameter descriptions. The description adds context by explaining each endpoint's purpose, but the parameter descriptions in the schema are already sufficient. The description adds limited extra semantic value 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?

The description clearly states the tool as a global deal intelligence API and lists specific endpoints (store, item, compare, etc.) with brief purposes. This distinguishes it from sibling tools like financial data (cryptopulse) or health (biopulse).

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?

The description lists endpoints and their uses, implying when to use each, but does not explicitly state when NOT to use this tool or alternatives. No guidance on prerequisites or selection among sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server