Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

search

Read-onlyIdempotent

Search Human Edge Press content in natural language to find screen-free children's books, blog essays, neuroscience and AI-literacy writing, Socratic playbooks, and developmental concepts, then fetch an ID for full text.

Instructions

Unified search across Human Edge Press's screen-free children's books, blog articles, neuroscience & AI-literacy essays, Socratic playbooks, and developmental concordance. Returns {results: [{id, title, url}]}; call fetch with an id for full text and metadata.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language search query across books, blogs, parenting challenges, or neuroscience concepts (e.g. 'high contrast baby book', 'transfer deficit', 'patience book', 'human veto AI')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing the return shape ({results: [{id, title, url}]}) and the handoff to fetch. Missing are result-count limits or pagination behavior, which would matter for a search tool.

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

Conciseness5/5

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

Two sentences, no waste, with the scope statement front-loaded and the return/handoff detail second. Every clause carries information an agent needs.

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 one-parameter read-only search with no output schema, the description supplies scope, return shape, and next-step routing, which is nearly everything needed. The remaining gap is behavioral detail about result volume (how many hits, whether results are truncated or ranked), which affects how an agent should query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single query parameter is fully documented with examples. The description adds meaning beyond the schema by characterizing the corpus the query spans (books, blogs, parenting challenges, neuroscience concepts), which helps the agent phrase queries appropriately.

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 ('Unified search') and enumerates the resource scope precisely: books, blog articles, essays, playbooks, concordance. The word 'unified' implicitly contrasts with the narrower scoped siblings (search_blogs_and_essays, search_human_edge_books), though it never names them explicitly, which keeps it just short of a 5.

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?

Gives clear in-workflow guidance: call fetch with an id for full text and metadata, which correctly routes the agent to the follow-up tool. It does not state when to prefer the scoped search siblings over this unified one, so the alternative-selection guidance is implied rather than explicit.

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