Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

search_human_edge_books

Read-onlyIdempotent

Find screen-free children's books, Pre-K workbooks, and gift sets by age, skill, virtue, format, occasion, or price, with developmental goals and checkout links.

Instructions

Search Human Edge Press's live-synced catalog of 100% screen-free children's books, Pre-K workbooks, and developmental gift box sets (ages 0–8). Use for queries like 'high-contrast newborn book', 'science board book for a 3 year old', 'children\'s book about patience or bravery', 'screen-free Pre-K workbook', or 'baby shower book bundle'. Filter by keyword, child age/stage, series, virtue/skill, format, occasion, or price. Returns book URLs, developmental goals, sample Socratic parent prompts, and 1-click Shopify checkout links.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum books to return (default: 6, max: 28)
queryNoNatural-language keyword query (e.g. 'baby faces', 'science', 'engineering', 'patience', 'brave', 'listening', 'pre-k workbook', 'master library')
formatNoBook format filter ('Board Book', 'Hardcover Book', 'Activity Workbook', 'Gift Set', 'Collector Edition')
seriesNoBook series filter (e.g. 'High-Contrast Baby Series', 'STEAM Alphabet Series', 'The Human Edge Series', 'Activity Workbooks', 'Curated Bundles & Gift Sets')
sortByNoSort order: 'relevance' (default), 'stage', 'price-low', or 'price-high'
ageStageNoAge or stage filter (e.g. 'newborn', '0-2', '2-4', '3-5', '3-7', '0-7', '4 years old')
maxPriceNoMaximum price in USD (e.g. 25, 60, 100)
minPriceNoMinimum price in USD
occasionNoGifting or learning occasion (e.g. 'Baby Shower', 'Birthday', 'Homeschool', 'Kindergarten Readiness')
virtueOrSkillNoSpecific virtue, STEAM subject, or developmental skill (e.g. 'brave', 'kind', 'patient', 'persistent', 'focused', 'honest', 'empathetic', 'listening', 'curious', 'creative', 'thankful', 'helpful', 'science', 'engineering', 'math', 'visual-tracking')
includeStudioPreviewsNoInclude upcoming 'In the Studio' preview series (Oddlings Workbooks, First Think First Words, Human Edge Stories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful context beyond annotations: the catalog is live-synced, results include URLs, developmental goals, Socratic parent prompts, and checkout links, and preview series are opt-in. It still does not discuss result limits beyond the schema or ranking behavior.

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?

The description is front-loaded with the core purpose and catalog scope, then examples, filters, and return values. It is dense but every sentence contributes useful selection context, though a few marketing phrases such as '100% screen-free' are less essential than the functional details.

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?

With 11 optional parameters, no output schema, and full schema coverage, the description does a good job explaining return content and filter dimensions. It is nearly complete, but it could better distinguish itself from the generic `search` sibling and clarify how results are ranked or paginated.

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?

Schema description coverage is 100%, so every parameter is already documented in the input schema, including examples for query, ageStage, virtueOrSkill, format, series, occasion, and price. The description reinforces the filter categories but adds little parameter-level meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 uses a specific verb and resource: search Human Edge Press's live-synced catalog of children's books, workbooks, and gift sets for ages 0–8. It clearly states the domain and product types, but it does not explicitly distinguish this tool from the sibling `search` tool or explain why an agent should pick this one over generic search.

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?

It gives concrete example queries and lists filter dimensions (keyword, age/stage, series, virtue/skill, format, occasion, price), which clearly signals when the tool is appropriate. It does not state when not to use it or name alternatives such as `get_book_details_and_parent_prompts` for detail lookups, so guidance is strong but lacks exclusions.

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