Skip to main content
Glama

Vinylscout — Dutch Vinyl LP & Record Player Prices

Get Dutch LP price index

get_lp_price_index
Read-onlyIdempotent

Get the monthly Vinylscout LP-prijsindex: median and mean lowest new LP price in the Netherlands, number of tracked albums, and same-album month-over-month and year-over-year changes (CC BY 4.0).

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_lp_price_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoNumber of most recent months to return (1–36, default 12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context — the upstream source (Vinylscout) and the CC BY 4.0 licence — but says nothing about data freshness, update cadence, or units, which is what would be most useful beyond the 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?

A single front-loaded sentence that leads with verb and resource before listing returned metrics. Every clause is substantive return-content information; there is no filler or redundant restatement of the title.

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?

There is no output schema, so the description must convey what comes back, and it does so thoroughly (median, mean, album count, MoM and YoY deltas). It is nearly complete for a one-parameter read tool; the only omissions are currency units and whether deltas are percentages or absolute values.

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% and the single 'months' parameter is fully documented in the schema (range 1–36, default 12). The description does not mention the parameter at all, so the baseline 3 applies — the schema carries the semantics entirely.

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?

States a specific verb ('Get') plus a precisely named resource ('monthly Vinylscout LP-prijsindex') and then enumerates exactly what the index contains: median and mean lowest new LP price, album count, and same-album MoM/YoY changes. Nothing about the output subject matter is left ambiguous, and it is clearly distinct from sibling price tools like get_album_prices.

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 scope ('Netherlands', 'monthly') implies the appropriate context, but the description never says when to prefer this index over sibling tools such as get_album_prices or get_vinyl_deals, and gives no exclusions. Usage is inferable from the narrow subject matter rather than stated.

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.