Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

get_series_books

Read-onlyIdempotent

Retrieve every book in a specified Human Edge Press series or collection by handle or title, so you can browse complete sets such as baby books, workbooks, or bundles.

Instructions

Get all books inside a specific Human Edge Press series or collection (e.g. 'high-contrast-baby-books', 'steam-board-books', 'human-edge-series', 'pre-k-workbooks-and-readiness', or 'curated-bundles-and-gift-sets').

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": {
      "seriesHandleOrTitle": "<seriesHandleOrTitle>"
    },
    "name": "get_series_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax books to return (default: 15)
seriesHandleOrTitleYesCollection/series handle or title (e.g. 'high-contrast-baby-books', 'steam-board-books', 'human-edge-series', 'bundles')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the domain of valid series identifiers; it says nothing about ordering, pagination behaviour, or what happens when a handle is unknown.

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 no filler, and the resource and scope come first. The list of five example handles is somewhat redundant with the schema's own examples, which is the only minor waste.

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?

For a simple read tool with no output schema and full annotation coverage, the definition is workable, but it never says what a returned book contains (full details versus identifiers) or how many results to expect given the limit cap of 28.

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 description simply recycles the same handle examples already present in the schema, adding no new meaning. The limit parameter and its default of 15 are not mentioned at all in the description, but that gap is filled by the schema.

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 all books inside a specific Human Edge Press series or collection', with concrete handle examples. It implicitly distinguishes itself from list_book_series_and_collections by scoping to books within one series, but never names that sibling to confirm the split.

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 only implied by the word 'specific' and the handle examples; there is no explicit statement of when to choose this over list_book_series_and_collections or search_human_edge_books, and no exclusions or prerequisites.

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