nmlp_get_pillar_guides
Get NMLP's pillar guide manifest — 60+ Southwest author/publisher authentication and pricing guides.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
New Mexico Literacy Project
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states what the tool retrieves without mentioning side effects, safety, 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?
The description is a single, concise sentence that conveys the essential purpose without extraneous detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the zero parameters and no output schema, the description is adequate but could provide more context about what the manifest contains or how to use the result.
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?
No parameters exist, so baseline score is 4 per guidelines. The description does not add parameter info, but none is needed.
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 verb 'Get' and the resource 'NMLP's pillar guide manifest', and distinguishes from sibling tools by its specific subject matter (60+ authentication and pricing guides).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or when not to use it.
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.
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.