Skip to main content
Glama

Vinylscout

Get record player details and replacement needle

get_record_player
Read-onlyIdempotent

Get verified specifications, live per-shop prices (Coolblue, bol.com, Conrad), and the compatible replacement needle for a specific record player slug (obtain slug from compare_record_players).

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

Input Schema

NameRequiredDescriptionDefault
slugYesRecord player slug from compare_record_players.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value by naming the data sources (Coolblue, bol.com, Conrad) and the nature of the price data as 'live', which is consistent with openWorldHint=false since the shop set is fixed.

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, zero filler, front-loaded with the payload an agent cares about (specs, prices, needle) and ending with the required input. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating what comes back: specifications, live per-shop prices and the compatible replacement needle. Combined with the upstream slug source, an agent has everything needed to call it correctly.

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% for the single slug parameter, and the description's only added detail — where the slug comes from — is already stated in the schema's parameter description. Baseline 3 applies when the schema does all the semantic work.

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: verified specifications, live per-shop prices and a compatible replacement needle for one record player slug. The resource is unambiguously a single record player, which separates it from album-price and price-index siblings without needing to name them.

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 an explicit prerequisite — the slug must come from compare_record_players — which tells the agent the correct upstream call before invoking this one. It stops short of stating when not to use it (e.g. shopping for an album instead), so it is clear context rather than full routing 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