Alex Polonsky's Personal MCP

Alex Polonsky - Music Discoveries

discover_music

Read-only

Explore algorithmic music picks from Alex Polonsky's public Albums and EPs archive, with unique artists. Choose surprise (random), across_decades (varied known release decades), or newer_releases (release dates wholly within the last 24 months through today). Year, month, or day date precision is preserved; ambiguous boundary dates and future releases are excluded from newer_releases. Repeated calls can give another selection. Picks are not personalized or Alex's recommendations. No genre, mood, popularity, or obscurity inference is supported. No artist, title, or query lookup.

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

Input Schema

Name	Required	Description	Default
`mode`	No		surprise
`count`	No

Output Schema

Name	Required	Description	Default
`note`	Yes
`count`	Yes
`items`	Yes
`fetched_at`	Yes
`source_url`	Yes
`attribution`	Yes
`selection_basis`	Yes
`snapshot_version`	Yes
`total_candidates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: repeated calls can yield different selections, picks are not personalized or recommendations, date precision is preserved, and ambiguous boundary dates and future releases are excluded from newer_releases. These details help the agent understand output variability and constraints without contradicting the readOnlyHint=true annotation.

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?

The description is front-loaded with the tool's purpose and then efficiently presents mode choices, behavioral constraints, and exclusions. Every sentence contributes useful information, and the structure supports quick scanning.

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?

Given that an output schema exists, the description need not explain return values. It covers the main behavioral and mode semantics, but the missing count parameter description leaves a small gap in completeness for a tool with two parameters.

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?

The mode parameter is well explained through the three mode descriptions, which compensates for the 0% schema description coverage. However, the count parameter is not described at all beyond its schema constraints, leaving half of the parameters without semantic guidance in the description.

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?

The description states a specific verb and resource: exploring algorithmic music picks from Alex Polonsky's public Albums and EPs archive. It clearly conveys the tool's purpose and the available modes. However, it does not explicitly distinguish this tool from sibling tools such as get_music_rotation, so it falls short of a 5.

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?

The description explains how to choose among the three modes and notes exclusions such as no artist/title/query lookup and no genre/mood/popularity/obscurity inference. It gives clear usage context but does not name sibling tools or say when to use this instead of them, so it is not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Alex Polonsky's Personal MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?