Skip to main content
Glama

Vinylscout

Get today’s Dutch vinyl deals

get_vinyl_deals
Read-onlyIdempotent

Get today’s genuine vinyl LP price drops in the Netherlands (albums at least 5% below their 30-day normal price), optionally filtered by price range and sorted by discount %, euros saved, or lowest price.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: "discount" (default, highest %), "saved" (most euros off), or "price" (lowest price).
limitNoMaximum deals to return (1–50, default 15).
max_priceNoOptional maximum LP price in EUR.
min_priceNoOptional minimum LP price in EUR.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds real domain behavior beyond that — the definition of a 'deal' as a 5%+ drop versus a 30-day baseline and a 'today' freshness window — but says nothing about return shape, whether prices include shipping, or how the daily snapshot is scoped by timezone, and no output schema exists to fill that gap.

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?

A single front-loaded sentence with the resource, geography, and qualifying rule stated before the optional filter/sort modifiers. Every clause carries information; there is no filler.

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?

For a zero-required-parameter read tool with a fully described schema and safety annotations, the description covers selection well. However, with no output schema, an agent still does not know what a returned deal contains (artist, album, shop, price, discount amount) or whether results are paginated, which is the main remaining gap.

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 description coverage is 100%, so all four parameters (sort with its three enum values, limit, min_price, max_price) are already documented in the input schema. The description only restates the filter and sort options at a high level, adding no format, currency, or interaction detail (e.g. min_price > max_price handling) beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Get today's genuine vinyl LP price drops') and pins the scope with a concrete inclusion rule: albums at least 5% below their 30-day normal price, in the Netherlands. That price-drop/discount framing is what separates it from generic siblings like search_vinyl or get_album_prices, so an agent can route here without opening the schema.

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 inclusion criterion (at least 5% below 30-day normal price, Dutch market, today only) implies when the tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that a full catalog search belongs to a different tool.

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