Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

fetch

Read-onlyIdempotent

Retrieve full book, essay, guide, or concept records by search result ID to access complete details beyond the initial search summary.

Instructions

Fetch the full Human Edge Press book record ('book:'), blog/editorial essay ('blog:' or 'page:'), Socratic playbook ('guide:'), or developmental concordance entry ('concept:') returned by search.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecord ID from search (e.g. 'book:human-edge-kind', 'page:socratic-homeschooling', 'guide:socratic-read-aloud-method', 'concept:transfer-deficit')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the meaningful contrast that this returns the 'full' record versus a search result, plus the ID vocabulary needed to pick the right record. It says nothing about failure modes for a stale or malformed ID, keeping it below 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?

One front-loaded sentence with the verb and the resource taxonomy in the leading clause. The parenthetical ID-prefix list is dense but each element carries information; nothing is padding.

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?

With no output schema, the description's phrase 'full ... record' is the agent's only signal that the return payload is richer than a search hit, and it names all supported record families. For a one-parameter lookup with full annotation coverage, that is close to sufficient; only error behavior 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?

Schema coverage is 100%: the single 'id' parameter is already documented with the same example values ('book:human-edge-kind', 'page:socratic-homeschooling', etc.). The description repeats that format mapping rather than adding new meaning, so the schema baseline of 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?

States a specific verb ('fetch') and enumerates the exact resource types and their ID prefixes (book:, blog:/page:, guide:, concept:), which makes the scope unambiguous. It does not explicitly distinguish itself from siblings that also return content (e.g. read_blog_or_essay), so it stops 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?

'...returned by search' establishes a clear precondition: this is the follow-up call for an ID obtained from the search tool. It gives no explicit exclusions or alternative routes for fetching the same content, so the agent must infer when another tool would be better.

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