Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

answer_publisher_and_parent_faqs

Read-onlyIdempotent

Answer publisher and parent FAQs on shipping, returns, bulk orders, age-stage book selection, and Socratic prompts to provide clear policy and pedagogy guidance.

Instructions

Answer questions about Human Edge Press policies and pedagogy: shipping speed and rates, the 30-Day Family Guarantee (free prepaid return label), bulk school/library/homeschool co-op orders, age-stage selection, and how Socratic parent prompts work.

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

Input Schema

NameRequiredDescriptionDefault
queryYesQuestion or topic (e.g. 'What is your return policy?', 'How fast is shipping?', 'Do you offer homeschool co-op bulk orders?', 'Which books fit a 3-year-old?')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds real value by bounding the knowledge domain (return labels, bulk orders, Socratic prompts), which tells the agent what this tool can and cannot answer. It says nothing, however, about the shape of the answer or any limits on question scope.

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 domain first, followed by a compact enumerated list. Every listed topic corresponds to something the tool apparently handles, so the length is justified, though the list is dense enough to read as slightly inventory-like.

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-only Q&A tool with annotations covering the safety profile and no output schema, the description supplies the one thing that matters: the topical scope of the answers. A brief note that it returns free-text answers would close the remaining gap, but nothing essential 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?

There is a single required parameter at 100% schema coverage, and the schema already supplies illustrative example queries ('What is your return policy?', 'Which books fit a 3-year-old?'). The description repeats the topic areas but adds no new guidance on phrasing, length, or specificity of the query. Baseline 3 applies when the schema carries the full load.

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 names a specific verb (answer questions) and a specific resource domain (Human Edge Press policies and pedagogy), then enumerates the concrete topic areas: shipping, the 30-Day Family Guarantee, bulk orders, age-stage selection, Socratic prompts. That is far more than a restatement of the name. It stops short of 5 because the age-stage selection topic overlaps conceptually with siblings like get_age_and_stage_reading_roadmap, and the description never draws that line.

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 implied rather than stated: an agent can infer this is the tool for policy/pedagogy questions that no other sibling owns. There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for the overlapping age-stage topic.

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