Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

recommend_books_and_bundles

Read-onlyIdempotent

Recommend personalized screen-free books and gift bundles by child age, occasion, budget, and learning goal, with developmental fit and checkout links.

Instructions

Recommend personalized screen-free books or gift box sets from Human Edge Press. Use for 'baby shower book gift', 'gift for a 1st / 3rd / 5th birthday', 'homeschool starter bundle', 'books for an anxious 4-year-old starting preschool', 'grandparent heirloom gift', or 'educational gift under $60'. Highlights bundle value, developmental fit, Socratic prompts, and 1-click checkout.

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

Input Schema

NameRequiredDescriptionDefault
childAgeNoChild's age or stage (e.g. 'newborn', '6 months', '2 years old', '4 years old', 'ages 0-7 siblings')
occasionNoOccasion (e.g. 'Baby Shower & Newborn Registry', 'Birthday', 'Homeschool Starter', 'Kindergarten Readiness', 'Holiday / Grandparent Gift', 'Classroom Library')
maxBudgetNoMaximum budget in USD (e.g. 25, 60, 100, 200)
learningGoalNoDevelopmental or character goal (e.g. 'tummy time vision', 'early science & engineering', 'patience & emotional regulation', 'bravery', 'complete screen-free library')

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?

Because readOnlyHint=true and idempotentHint=true are already annotated, the description does not need to establish that this is a safe read, but it still does not say what a recommendation consists of: titles, bundle contents, or links. The mention of '1-click checkout' is ambiguous and could be misread as a transactional capability, though it most plausibly describes what the results highlight.

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

Conciseness3/5

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

The purpose sentence is front-loaded and clear, but the long run-on list of quoted shopper phrases is padded, and the closing marketing sentence about 'Socratic prompts, and 1-click checkout' adds promotional weight rather than operational information.

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?

For a read-only, no-required-parameter recommendation tool with fully documented parameters, the description covers the domain and the buyer scenarios needed to call it. Return shape is unexplained, but that is a minor gap given its simplicity and the lack of an output schema.

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%, and the schema already gives example values for childAge, occasion, budget, and learningGoal. The description's examples echo those occasions and budgets without adding format rules, defaults, or guidance on combining the parameters, so it does no more than the schema baseline.

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: 'Recommend personalized screen-free books or gift box sets from Human Edge Press.' That clearly separates it from search_human_edge_books and get_book_details_and_parent_prompts, which retrieve existing records rather than generating a recommendation. It stops short of naming a sibling explicitly, so it stays at 4.

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 quoted shopper intents ('baby shower book gift', 'homeschool starter bundle', 'educational gift under $60') give concrete situations for using the tool. However, there is no guidance on when not to use it, or on when to prefer search_human_edge_books or generate_direct_checkout_link.

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