Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

search_blogs_and_essays

Read-onlyIdempotent

Search Human Edge Press blogs, neuroscience essays, Socratic homeschooling guides, and parent research to answer questions on screen time, reading, early STEAM, teen social media, and AI literacy.

Instructions

Search Human Edge Press's blog articles, developmental neuroscience essays, Socratic homeschooling stances, and parent research guides. Use when answering questions about screen time effects ('Transfer Deficit', 'Cortical Thickness Crisis'), 'Serve & Return' parent reading, Socratic homeschooling, early STEAM, teen social media dopamine loops, or young adult AI literacy ('The Human Veto'). Returns canonical URLs, key takeaways, scientific concepts, and paired books.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax articles/essays to return (default: 6)
queryNoTopic or research question (e.g. 'transfer deficit', 'socratic homeschooling', 'teen social media focus', 'young adults AI human veto', 'screen-free resources')
topicPillarNoOptional topic pillar filter

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the return contents (canonical URLs, key takeaways, scientific concepts, paired books), which matters because there is no output schema. It omits behavior details like ranking or pagination, keeping it from a 5.

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?

The definition is front-loaded with the resource scope and then the usage condition, and every sentence contributes either scope or return information. It is somewhat dense with quoted buzzwords, but that specificity aids selection rather than wasting space.

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, closed-world search tool with three optional, fully documented parameters and annotations covering the safety profile, the description supplies enough: what it searches, when to use it, and what it returns. The absence of output schema is offset by the return-value summary; only alternative-tool routing 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 description coverage is 100%, with each parameter documented including enum values and an example-laden query description, so the schema carries the burden. The description's topic examples loosely mirror the query parameter's examples but add no new syntax or constraint information beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Search') plus a precise resource set (blog articles, essays, Socratic homeschooling stances, parent research guides) and even enumerates the named concepts it covers. It distinguishes this from the sibling book-search and single-article tools without needing the schema.

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 'Use when answering questions about...' clause gives clear positive triggering conditions with concrete topic examples (transfer deficit, serve & return, teen dopamine loops). It does not state when NOT to use it or name an explicit alternative such as search_human_edge_books or read_blog_or_essay, so it stops short of full routing guidance.

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