Skip to main content
Glama

Vinylscout

Get album prices across Dutch shops

get_album_prices
Read-onlyIdempotent

Get full per-shop prices (plate price, Dutch shipping cost, total price), price history summary, EAN, and canonical URL for a specific vinyl album slug (obtain slug from search_vinyl).

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": {
      "slug": "<slug>"
    },
    "name": "get_album_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCanonical album slug from search_vinyl, e.g. "pink-floyd-the-dark-side-of-the-moon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds return-shape context (price breakdown, history summary, EAN, URL), which is useful, but says nothing about shop coverage, data freshness, or behavior when the slug is unknown or has no listings.

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 tight sentence with no filler, front-loading the returned fields and ending with the required input and its source. Nothing is redundant or padded.

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 single-parameter read tool with no output schema, enumerating the returned fields plus the slug prerequisite covers the essentials an agent needs to call it correctly. Minor gaps remain around no-data/error behavior and whether results span all Dutch shops, preventing a 5.

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 parameter already documents itself with the same 'canonical album slug from search_vinyl' wording and example. The description's mention of provenance and canonical form reinforces the schema but adds little beyond it, 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?

States a specific verb and resource ("Get full per-shop prices ... for a specific vinyl album slug") and enumerates exactly what comes back: plate price, Dutch shipping, total, price history summary, EAN, canonical URL. This clearly differentiates it from search_vinyl, which it names as the slug source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition and routing cue: the slug must come from search_vinyl, which tells the agent to run discovery first. It lacks an explicit exclusion (e.g., when to use get_vinyl_deals or get_lp_price_index instead), so it falls short of full when/when-not guidance.

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