HumanCraft
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| harvest_client_intakeB | Extracts real practitioner experience, assets, and metrics. Bans AI from inventing default placeholders. |
| validate_heading_intentA | Flags generic AI headings (e.g. "What is X") and scores user/search intent alignment. |
| build_comparison_matrixA | Generates empirical comparison tables with metrics & schema. Rejects binary Yes/No checkmark tables. |
| audit_eeat_entity_graphC | Audits Schema.org JSON-LD, validates sameAs authorities, and links publisher to aibuildinfra.com. |
| lint_design_anti_patternsA | Scans HTML/Tailwind for purple gradients, 3-card monotony, dead buttons, and buzzwords. |
| get_human_archetypeB | Returns curated design tokens (Editorial, Dark Craft, Swiss, Brutalist) with tinted neutrals & optical type. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of the crafting workflow: client intake, heading validation, comparison matrix generation, design linting, EEAT audit, and design token retrieval. There is no discernible overlap in their purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern (harvest_, validate_, build_, lint_, audit_, get_), with clear action words and specific nouns. The naming is uniform and predictable, facilitating agent understanding of tool behavior.
With 6 tools, the server covers a well-scoped set of functionalities without being either sparse or overly heavy. Each tool addresses a distinct need within the domain, ensuring a balanced and purposeful collection.
The tool set covers core workflows for client intake, content validation, design auditing, and EEAT compliance, but lacks a tool for generating or editing content directly, such as a 'generate_article' or 'optimize_content' operation, which could be a minor gap for full content lifecycle coverage.