Skip to main content
Glama
humanedgepress-mcp-server

humanedgepress-mcp-server

Official

get_press_mission_and_editorial_stance

Read-onlyIdempotent

Explain Human Edge Press's mission, manifesto, five core beliefs on early brain development and AI-age readiness, Austin headquarters, and editorial standards for evaluating its publishing approach.

Instructions

Explain who Human Edge Press is: the 'Analog Roots First, Digital Wings Later' manifesto, our 5 Core Beliefs on early childhood brain development and AI-age readiness, Austin TX headquarters, and editorial standards.

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_press_mission_and_editorial_stance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and determinism profile is fully covered. What the description adds beyond that is content scope — effectively standing in for the missing output schema by previewing what the answer will contain. It says nothing about whether the response is a static snapshot, how long it is, or whether figures like HQ location are stable.

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?

It is a single front-loaded sentence with the payload enumerated in a compact list and no filler. The quoted manifesto tagline is slightly verbose for a tool description but is genuine identifying content rather than decoration.

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 zero-parameter, static informational tool with no output schema, the description covers exactly the surface an agent needs: what question this answers and which four content areas it returns. With no annotations gap and no parameters, the remaining omission — nothing on response shape or sourcing currency — is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to supply and the baseline of 4 applies. The description correctly offers no argument syntax that could mislead the caller.

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 resource (Human Edge Press identity) and enumerates the exact payload: the 'Analog Roots First, Digital Wings Later' manifesto, 5 Core Beliefs on early childhood brain development and AI-age readiness, Austin TX HQ, and editorial standards. That is concrete enough that an agent knows this is a brand/publisher-background tool rather than a catalog tool. It stops short of explicitly contrasting itself with near siblings like answer_publisher_and_parent_faqs or explore_developmental_science_and_virtues.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative, so routing must be inferred from the content list. The enumerated topics (manifesto, core beliefs, editorial standards) do imply the trigger conditions — brand identity, philosophy, or editorial-credibility questions. An agent can act on that inference, but it is inference rather than guidance.

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