Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

list_book_series_and_collections

Read-onlyIdempotent

Lists Human Edge Press book series, developmental stage collections, gift bundles, and optional 'In the Studio' previews with age ranges, book counts, descriptions, and URLs.

Instructions

List all Human Edge Press book series, developmental stage collections, curated gift bundles, and upcoming 'In the Studio' preview lines with age ranges, book counts, descriptions, and URLs.

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

Input Schema

NameRequiredDescriptionDefault
includeStudioPreviewsNoInclude upcoming 'In the Studio' lines (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value by disclosing what each listing carries (age ranges, book counts, descriptions, URLs), which matters because no output schema exists. It does not mention ordering or result-size behavior, a minor 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?

One front-loaded sentence with the verb first and no filler. The enumerated noun list is dense but each item is a distinct resource type an agent would want to know is included, so little is wasted.

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 zero-required-parameter read-only catalog tool with no output schema, the description covers both what is returned and its fields. The main missing piece is guidance on how the results are structured/grouped and when to prefer a narrower sibling tool.

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 single optional boolean already documents its default of true. The description's mention of "upcoming 'In the Studio' preview lines" gives semantic grounding for what that flag toggles, but adds no further format or interaction detail. 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?

Specific verb ("List") plus an enumerated set of resources: book series, developmental stage collections, gift bundles, and 'In the Studio' preview lines. An agent can tell this is the catalog-browsing tool rather than a book-detail or book-search tool, though it never names a sibling to contrast with.

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 resource enumeration: an agent infers this is for surveying the overall catalog structure. There is no explicit statement of when to use this instead of get_series_books, search_human_edge_books, or recommend_books_and_bundles, 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.