Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

get_socratic_reading_and_unit_study_guide

Read-onlyIdempotent

Retrieve step-by-step parent and homeschooler playbooks for screen-free daily routines, Socratic read-aloud questioning, infant reading, STEAM unit studies, teen focus, and AI literacy.

Instructions

Retrieve Human Edge Press's step-by-step parent and homeschooler playbooks: (1) Analog Roots 0–7 daily screen-free blueprint, (2) Socratic Read-Aloud questioning method (LOOK • FEEL • CONNECT • TRY), (3) Month-by-month newborn high-contrast reading routine (0–24m), (4) 5-day screen-free kitchen-table STEAM unit study (ages 2–5), (5) Teen focus & social media ground rules, and (6) Young adult 'Human Veto' AI literacy rules.

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

Input Schema

NameRequiredDescriptionDefault
topicNoPlaybook slug, or 'all' to list every available playbook

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description's added value is the content inventory — which six playbooks exist — but it says nothing about return shape (full prose vs. links), depth, or whether the 'all' path returns summaries.

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

Conciseness3/5

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

The lead clause is well front-loaded with verb and resource, but everything after it is one long run-on numbered enumeration, and fragments like '(LOOK • FEEL • CONNECT • TRY)' are marketing texture rather than selection-relevant detail. The content is dense enough to justify length, but the structure makes it harder to scan than it needs to be.

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 single-optional-parameter, read-only content fetch with strong annotations and no output schema, the description covers what an agent needs to choose a topic and call the tool. The remaining gap — what the response actually looks like for a topic versus 'all' — is minor at this complexity level.

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 enum already documents all seven accepted values including 'all', so the baseline is 3. The description loosely maps human-readable playbook titles onto those slugs, but it omits 'all' entirely and adds no matching rules, so it neither compensates nor enriches the schema meaningfully.

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?

The description uses a concrete verb ('Retrieve') plus a clearly bounded resource (parent/homeschooler playbooks) and enumerates the six specific playbooks, so an agent knows exactly what content this returns. It does not, however, differentiate itself from adjacent siblings like get_age_and_stage_reading_roadmap or get_book_details_and_parent_prompts, leaving overlap resolution to inference.

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: the enumerated playbook topics suggest the situations the tool serves (screen-free routines, read-aloud method, teen rules), but there is no explicit 'use this when…' statement, no exclusions, and no named alternative for roadmap or book-specific questions. An agent must infer routing from the sibling list.

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