New Mexico Literacy Project

nmlp_vinyl_lookup

Identify a vinyl record from the matrix/runout etching in the deadwax (stamper suffixes vary copy to copy, so stable-prefix matching is built in), the label catalog number, or the barcode. Returns artist, album, year, label, catalog number. Backed by NMLP's Discogs-derived vinyl identifier index plus MusicBrainz fallback. Human tool (with a Goldmine-style grading checklist): https://newmexicoliteracyproject.org/vinyl-lookup

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	Yes	The deadwax etching, catalog number, or barcode as read, e.g. 'XSM 156097', 'SD 19129'

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses stable-prefix matching, fallback to MusicBrainz, and links to a grading checklist. Does not specify rate limits or error handling, but adds useful behavioral context.

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?

Three sentences, each valuable. Purpose stated first, followed by behavior and fallback, then link. No fluff.

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?

For a single-parameter lookup tool without output schema, the description fully covers input types, fallback, and return fields. Link adds optional depth.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema by explaining what 'identifier' can be (deadwax etching, catalog number, or barcode) and providing examples. Schema coverage is 100%.

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 clearly states the tool identifies vinyl records from matrix/runout etching, catalog number, or barcode, and returns artist, album, year, label, catalog number. This distinguishes it from siblings like nmlp_cd_lookup.

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 specifies when to use the tool (for vinyl records) and mentions fallback sources, but does not explicitly exclude other media or provide when-not guidance. Context is clear.

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

All New Mexico Literacy Project tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose, from specific identifier lookups (CD, vinyl, LCCN) to donation logistics and first-edition identification. The general resolver (nmlp_resolve) is complementary and well-differentiated.

Naming Consistency5/5

All tools follow a consistent pattern: 'nmlp_' prefix with descriptive snake_case names (e.g., nmlp_check_coverage, nmlp_identify_first_edition). There is no mixing of conventions.

Tool Count4/5

At 16 tools, the count is slightly above the ideal 3-15 range, but each tool serves a non-trivial and distinct function across book identification, media lookup, and donation management, justifying the number.

Completeness4/5

The server covers core identification workflows (first editions, number lines, publisher rules, various identifiers) and donation operations, but lacks appraisal/pricing tools and more granular donation status tracking, which are minor gaps.

Resources

Need Help?