Skip to main content
Glama

New Mexico Literacy Project

by org.newmexicoliteracyproject

nmlp_identify_first_edition

Identify whether a specific book is a first edition. Given a title (and optionally author), returns that title's POINTS OF ISSUE — the exact details that mark a true first printing — plus true-first precedence (US vs UK), book-club/reprint tells, publisher, year, the human-readable page URL, and a citation. THE tool for 'how do I tell if my copy of X is a first edition.' Draws on 6,700+ independently-verified titles (CC BY 4.0, DOI 10.5281/zenodo.21184548).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesBook title (series/subtitle suffixes are fine).
authorNoAuthor name — strongly improves match accuracy for common titles.

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries burden. Discloses returned fields, data source, and licensing, but does not mention error handling, speed, or limitations.

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?

Single paragraph, efficient. Every sentence contributes: purpose, required inputs, output contents, data source. No redundant words.

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?

Comprehensive for tool with no output schema: describes all returned elements, data source, licensing. Lacks mention of what happens if title not found or error cases.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. Description adds value by noting 'series/subtitle suffixes are fine' for title and that author 'strongly improves match accuracy'.

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 identifies if a book is a first edition, specifying the verb 'identify' and resource 'first edition status'. Distinguishes itself from siblings by being 'THE tool' for this specific question.

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

Usage Guidelines3/5

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

Implies usage by stating 'Given a title (and optionally author)' and returns details, but does not explicitly state when not to use or contrast with sibling tools like nmlp_decode_number_line.

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 toolsInspect
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