Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

read_blog_or_essay

Read-onlyIdempotent

Retrieve full Markdown, headings, scientific takeaways, citation URL, and paired book recommendations for Human Edge Press blog posts, essays, or Socratic guides by ID, slug, or URL.

Instructions

Read the full clean Markdown text, section headings, scientific takeaways, canonical citation URL, and paired book recommendations for any Human Edge Press blog post, editorial essay, or Socratic guide.

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": {
      "slugOrId": "<slugOrId>"
    },
    "name": "read_blog_or_essay"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugOrIdYesArticle ID, slug, or URL (e.g. 'socratic-homeschooling', 'teen-social-media', 'young-adults-ai', 'tools', 'page:socratic-homeschooling', 'guide:socratic-read-aloud-method')

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 establish readOnly, idempotent, non-destructive, closed-world access, so the safety profile is covered. The description adds genuine value by disclosing the returned payload (clean Markdown, headings, takeaways, canonical URL, book recommendations), which matters since no output schema exists. It omits error behavior for unknown slugs and any rate limits.

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 sentence with the resource front-loaded and the return contents enumerated in a compact list. It is dense but every clause adds information; no filler.

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-parameter read tool with full annotation coverage and no output schema, the description conveys enough: what it fetches, in what form, and what extras come back. Only the failure case for a bad slug is unaddressed.

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?

Only one parameter, slugOrId, and the schema already carries a 100% description with concrete example values ('socratic-homeschooling', 'page:...', 'guide:...'). The description adds no meaning about precedence between ID, slug, and URL forms, so 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?

Uses a specific verb (Read) plus an enumerated resource: full Markdown text, section headings, scientific takeaways, canonical citation URL, and paired book recommendations from Human Edge Press. That is far more specific than 'get post', and the mention of 'socratic guide' widens scope knowingly. It stops short of naming the sibling it supersedes (search_blogs_and_essays), so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: this reads one item by slug/ID/URL, which contrasts with the search-style siblings, but the description never says 'use after searching' or 'do not use for discovery'. No exclusions or prerequisites are stated.

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