Skip to main content
Glama
Procurement MCP

Procurement MCP

by belikh

latest_deals

Fetch newly posted community deals from OzBargain and Cheapies, ranked by votes and filterable by keyword, minimum votes, or source, with expiry and parsed price returned for each deal.

Instructions

List the newest community-posted deals, most upvoted first.

Reads the sites' own RSS feeds, which hold about the latest 100 deals each. Each deal carries votes, comment count, expiry and the price parsed from its title. A feed that fails adds one kind='diagnostic' entry.

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": "latest_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeep only deals whose title, brand or tags contain one of these words
sourcesNoDeal sites to read. Default: ozbargain. cheapies is a New Zealand site priced in NZD.
min_votesNoKeep only deals with at least this many net votes
max_resultsNoCap on deals returned

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by disclosing the data source (the sites' own RSS feeds), the ~100-item window per site, the fields each deal carries, and the failure mode ('a feed that fails adds one kind="diagnostic" entry'). It says nothing about auth, rate limits, caching freshness, or what an empty result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary action and ordering, and no filler. The RSS-window and diagnostic-entry caveats are tightly compressed into single lines rather than being buried or repeated.

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?

An output schema exists, so return values need not be explained, and the description is proportionate to a 4-parameter read-only list tool. It still leaves gaps around result freshness and how this differs from the search tools, which an agent needs in order to choose 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 baseline is 3 and the schema already explains query, sources, min_votes and max_results. The description adds a little beyond it: the ~100-item per-feed ceiling gives max_results meaningful context, and the note that cheapies is priced in NZD is echoed from the schema.

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 gives a specific verb and resource ('List the newest community-posted deals') plus an explicit ordering ('most upvoted first'), which is enough for an agent to know what it returns. It does not name or differentiate itself from siblings such as search_offers or get_offer_detail, so the agent must infer the boundary itself.

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?

No explicit when-to-use or when-not-to-use statement, and no alternative is named. Usage is only implied by the scope note that feeds hold 'about the latest 100 deals each', which hints this is a recent-listing tool rather than a search or lookup tool.

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