Skip to main content
Glama

deals

by com.kitsdeals

Register a deal watch

register_watch

Register a standing deal watch. Writes the intent to the sourcing pipeline and returns delivery channels: a one-time token-gated Atom feed plus an optional webhook that activates after interpretation. Progress and live matches are available through check_watch using the returned watch_id. A concrete model_number usually auto-promotes; family intents can require review. conditions defaults to new and open_box.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specsNoStructured spec/attribute constraints. Pass these whenever the human names a hard requirement. Keys are generated from docs/spec-keys.json: numeric <spec_key>_min/_max (an exact 8 TB drive is storage_gb_min: 8000 plus storage_gb_max: 8000), enum/list <spec_key>_in (camera_type_in, bundle_includes_in), and boolean direct keys (bundle). Storage uses decimal GB: 1 TB = 1000 GB. Unknown keys are rejected; deals missing the constrained spec are excluded (must-have semantics). Deterministic intent extraction is a fallback; explicit specs always override it, and soft phrasing ("around 65 inches") is never auto-constrained.
intentYesFree-text intent (e.g. "Oura Ring 4 silver under $350"). The interpretation pipeline owns the structuring.
agent_idNoSelf-identifier for telemetry (e.g. "claude-desktop:tom"). Helps us prioritize agent demand.
conditionsNoAccepted deal conditions. Defaults to new + open_box. During consent, surface all four categories and ask whether to add refurbished/pre_owned or restrict to new only.
model_numberNoManufacturer model number (MPN) for the exact variant — e.g. "K-65XR70" for the Sony BRAVIA 7 65". A concrete MPN auto-promotes in ~60s; family-level intents without one require operator review (hours).
max_price_centsNoHard price ceiling for delivery, in cents (a numeric string like "150000" is accepted).
min_discount_pctNoMinimum discount percentage for delivery.
webhook_callback_urlNohttps:// endpoint to receive push deliveries (activates post-interpretation).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/non-idempotent nature is already disclosed. The description adds valuable behavior beyond annotations: it writes to the sourcing pipeline, returns a one-time token-gated feed plus optional webhook, and explains auto-promotion vs. review. It does not contradict annotations.

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?

The description is three sentences, front-loads the core verb and resource, and each sentence earns its place: delivery channels, check_watch linkage, auto-promotion/review behavior, and the conditions default. No wasted words.

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?

Given the complexity (8 params, nested objects, 0 enums in top-level, no output schema), the description covers the key agent-relevant workflow: what the tool does, what it returns conceptually, where to check results, the model_number nuance, and the conditions default. It does not enumerate all delivery channel details or error cases, but the schema covers parameter semantics and the description provides enough operational context for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter. The description adds meaningful context beyond the schema: it explains what the webhook activation timing is ('after interpretation'), clarifies the auto-promotion behavior tied to model_number, and notes the default for conditions ('new and open_box'). This is above baseline because it connects parameters to workflow behavior.

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 states a specific verb ('Register'), a resource ('a standing deal watch'), and the key delivery mechanism ('returns delivery channels: a one-time token-gated Atom feed plus an optional webhook'). It distinguishes itself from check_watch, a sibling, by explicitly naming it as the place to see progress/live matches.

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?

The description provides clear context about when to use this tool: to register a standing watch, with delivery channels and a watch_id for later check_watch calls. It doesn't explicitly exclude alternatives or name when not to use it, but the sibling differentiation is implied through the check_watch reference and the description's overall purpose. It also mentions that a concrete model_number auto-promotes while family intents require review, which helps an agent decide what to include in the intent.

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

All deals toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct operation: discovery (get_deal, latest_deals, search_deals), watch lifecycle (register_watch, check_watch, cancel_watch), and feedback (report_outcome). The potential overlap between latest_deals and search_deals is resolved by their freshness/curation vs keyword-search framing. No two tools appear to do the same thing.

Naming Consistency4/5

Six of seven tools follow a clear verb_noun pattern (register_watch, check_watch, cancel_watch, get_deal, search_deals, report_outcome). 'latest_deals' breaks the pattern by using an adjective_noun noun phrase instead of a verb, but this is a minor deviation. Overall the convention is predictable.

Tool Count5/5

Seven tools is well-scoped for a deals discovery and watch-monitoring server. Each tool covers a distinct need and none feel redundant. This is within the ideal range and not bloated.

Completeness4/5

The core lifecycle is covered: discover deals, get details, register a watch, check its status, cancel it, and report outcomes. Missing a list/update watch operation is a minor gap, but cancel-and-re-register works as a workaround. For the stated purpose, no severe dead ends exist.

Resources