Skip to main content
Glama

Vinylscout

Search Dutch vinyl LP prices

search_vinyl
Read-onlyIdempotent

Search vinyl LP albums sold in the Netherlands by artist and/or album title. Returns canonical slugs, vinylscout.nl URLs, shop counts, and today’s cheapest price (excluding and including Dutch shipping).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_vinyl"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (1–25, default 10).
queryYesArtist name and/or album title, e.g. "Fleetwood Mac Rumours" or "Doe Maar".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds genuinely new context: it enumerates what comes back (canonical slugs, vinylscout.nl URLs, shop counts) and clarifies that pricing is today's cheapest both excluding and including Dutch shipping. It does not discuss result ordering, empty-result behavior, or currency, which keeps it below a 5.

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, zero filler, with the scope and the return payload front-loaded in that order. Nothing redundant given what the schema and annotations already carry.

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?

For a two-parameter read-only search with no output schema, the description supplies the essential missing piece: what the response contains and how prices are defined. Ranking behavior and pagination are absent but are minor against an otherwise complete picture.

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 both the query example and the limit bounds are already documented in the schema. The description's mention of artist and/or album title restates the schema rather than adding syntax or matching-rule detail, so the baseline 3 applies.

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?

States a specific verb (search) plus resource (vinyl LP albums) and a precise geographic scope (sold in the Netherlands), with the matching dimensions named (artist and/or album title). It stops short of distinguishing itself from siblings like get_album_prices or get_lp_price_index, which an agent must still disambiguate on its own.

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 phrase 'by artist and/or album title' implies the intended input context, so usage is inferable, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for a direct album lookup versus a search.

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