Skip to main content
Glama

deals

by com.kitsdeals

Report a deal outcome

report_outcome

Record what happened after a deal was acted on. Outcomes: purchased, deal_dead, wrong_price, out_of_stock, irrelevant, checkout_failed. Feedback feeds deal ranking, and deal_dead / wrong_price reports trigger fast removal of bad deals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoAnything else worth knowing.
deal_idYesThe deal id.
outcomeYesWhat happened.
actual_price_centsNoPrice actually seen/paid, in cents — include when it differed from ours.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate mutation (readOnlyHint false) but not destructive. Description adds that feedback feeds ranking and triggers fast removal for deal_dead/wrong_price. This provides extra behavioral context beyond 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?

Two sentences: first states purpose, second explains consequences. No wasted words, front-loaded with key information.

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?

Covers purpose, outcomes, and consequences. Lacks mention of prerequisites (e.g., need a valid deal_id from get_deal) but overall adequate for a simple reporting tool.

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%, so parameters are well-documented. Description repeats outcome enum but adds no additional meaning beyond the schema. Baseline score of 3 is appropriate.

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 records what happened after a deal is acted on, listing specific outcome options and their consequences. It distinguishes from sibling tools (watching, searching) which serve different purposes.

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?

Implies usage after acting on a deal, but does not explicitly state when not to use or provide alternatives. Sibling tools are distinct, so no confusion, but guidance could be more explicit.

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