Skip to main content
Glama

Vinylscout — Dutch Vinyl LP & Record Player Prices

List Dutch vinyl shops and shipping rates

list_vinyl_shops
Read-onlyIdempotent

List all 15 Dutch and European vinyl webshops tracked by Vinylscout with verified shipping rates to the Netherlands, free-shipping thresholds, album counts, median LP prices, and how often each shop is cheapest.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the result set is a fixed, bounded universe of exactly 15 tracked shops with 'verified' rates scoped to the Netherlands, telling an agent the data is curated and complete rather than a live search.

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?

One sentence, front-loaded with the scope ('all 15 Dutch and European vinyl webshops tracked by Vinylscout') followed by the returned fields. The dense field enumeration earns its space because no output schema exists to describe return values elsewhere.

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?

With no output schema, the description correctly shoulders the burden of describing what comes back, and with zero parameters and rich annotations there is little else required. Minor gaps remain: ordering of the list and whether rates/price figures are refreshed periodically are unstated.

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?

The tool takes no parameters, so the baseline is 4; there is no argument semantics for the description to clarify. Nothing in the description misleads about inputs.

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 opens with a specific verb and resource ('List all 15 Dutch and European vinyl webshops tracked by Vinylscout') and enumerates the payload it returns: shipping rates, free-shipping thresholds, album counts, median LP prices, and cheapest-frequency. The resource is categorically distinct from the siblings (deals, album search, price index, record players), so an agent can route to it 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?

Usage is implied rather than stated: an agent can infer this is the overview/shop-directory call used before drilling into deals or album prices, but no explicit when-to-use or when-not-to-use condition is given. With zero parameters there is little to get wrong, which keeps this adequate rather than deficient.

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.