Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

get_book_details_and_parent_prompts

Read-onlyIdempotent

Retrieve full details for a specific children’s book, workbook, or box set, including synopsis, character duo, Socratic parent prompts, neuroscience rationale, specs, and checkout links.

Instructions

Get complete details for a specific Human Edge Press book, workbook, or box set: full synopsis, child-and-animal character duo, built-in Socratic conversation prompts for parents, developmental neuroscience rationale, physical book specifications, and 1-click Shopify checkout links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bookHandleOrTitle": "<bookHandleOrTitle>"
    },
    "name": "get_book_details_and_parent_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookHandleOrTitleYesProduct handle (e.g. 'human-edge-kind', 's-is-for-science-steam-alphabet-board-book', 'baby-faces-high-contrast-board-book', 'master-screen-free-chest-bundle'), title, or numeric product ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds useful content-level disclosure — that responses include Socratic parent prompts, neuroscience rationale, physical specs and Shopify checkout links. It says nothing about behavior on a missing or mismatched identifier, which is the remaining meaningful gap.

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?

A single front-loaded sentence with the verb and scope first, followed by a compact list of returned artifacts. The list is long but every item is substantive and none is filler.

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 no output schema, the enumeration of returned fields (synopsis, character duo, parent prompts, rationale, physical specs, checkout links) does the job of telling the agent what comes back. For a one-parameter read tool with full annotation coverage, only the not-found behavior is missing.

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 coverage is 100% and the schema itself already documents that the field accepts a handle, title, or numeric product ID with four concrete examples. The description only restates that the target is a specific book, workbook, or box set, adding little beyond the structured field; baseline 3 applies.

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?

States a specific verb and resource ('Get complete details for a specific Human Edge Press book, workbook, or box set') and enumerates the payload, so an agent knows this is the single-item detail lookup. It never names a counterpart such as search_human_edge_books or list_book_series_and_collections, so the distinction from lookup-by-query siblings is left implicit.

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?

Usage is implied: fetch full detail for one already-identified product. The description does not say when to prefer this over search_human_edge_books or get_series_books, nor what to do if the identifier is ambiguous or unknown, leaving the routing decision to inference.

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