New Mexico Literacy Project

nmlp_resolve

One Box: resolve ANY physical-media identifier in one call — auto-detects the type (Library of Congress LCCN, ISBN-10/13, CD DIDX hub code, label catalog number, UPC/EAN barcode, vinyl matrix/runout etching) and returns ranked typed candidates across NMLP's 48M-record indexes (20.9M LCCN + 8.7M CD + 19M vinyl). ISBN input returns the exact Amazon listing link (ASIN=ISBN-10), never a title search. Misses return Attested Absence: exactly which indexes were checked at what dataset version, so 'not found' is usable evidence. Use this when you don't know what kind of number you have; use the specialized lookups when you do. Identification only — does NOT appraise or value items; NMLP never buys books. Human tool: https://newmexicoliteracyproject.org/lookup

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	Yes	Any identifier as printed/etched: '63-12345', 'DIDX 2113', 'CK 40999', a 12/13-digit barcode, an ISBN, or a deadwax matrix string. Dashes, spaces, case ignored.

TDQS

A4.7/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 auto-detection, ranked candidates, missed-index reporting with dataset versions, and the non-appraisal/non-purchase policy. Lacks explicit read-only statement but implies it. Good but not perfect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph, slightly long but well-structured. Front-loaded with purpose, then details, usage guidelines, and limitations. Could be broken into sections for readability.

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?

Given no output schema, description adequately explains return behavior (ranked candidates, Attested Absence) and covers key aspects for a complex resolve tool. Complete for its purpose.

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?

Schema coverage is 100% with a single parameter. Description adds context beyond schema: examples of valid inputs, case/format insensitivity, and special ISBN behavior (returns exact ASIN link).

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?

Clearly states the tool resolves any physical-media identifier, auto-detects type, and explicitly contrasts with specialized lookups like nmlp_cd_lookup, nmlp_lccn_lookup, and nmlp_vinyl_lookup.

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

Usage Guidelines5/5

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

Explicitly says when to use ('when you don't know what kind of number') and when not to ('use specialized lookups when you do'), plus states it only identifies, does not appraise or buy.

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?