Santismm Knowledge — Harness Engineering, Agentic AI & Governance

Get a Harness Engineering Handbook Chapter

get_handbook

Read-onlyIdempotent

Get one Harness Engineering Handbook chapter, by id (e.g. 'HRN-001') or slug. Returns the full Markdown body plus its provenance and related ids. Use this once search or list_handbook has given you an id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Chapter id like 'HRN-001', or its slug.
`locale`	No	Language of the returned body. Default: en.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`body`	No	Full Markdown body of the chapter.
`name`	No
`slug`	No
`tags`	No
`domain`	No
`locale`	No
`status`	No
`aliases`	No
`api_url`	No
`locales`	No
`related`	No
`summary`	No
`updated`	No
`version`	No
`category`	No
`evidence`	No	Evidence-First provenance: weight claims by this.
`fallback`	No	True when the body is not in the requested locale.
`featured`	No
`patterns`	No
`knowledge`	No
`frameworks`	No
`references`	No
`how_to_cite`	No	The citation, already formed — use it verbatim.
`resource_uri`	No
`technologies`	No
`canonical_url`	No
`resolved_locale`	No	The locale actually returned. Chapters are authored in English and translated; where a translation exists this equals the requested locale, and `fallback` says when it does not.
`requested_locale`	No	The locale that was asked for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedOutput schema / properties / how_to_cite

Added value: +{
+  "description": "The citation, already formed — use it verbatim.",
+  "type": "string"
+}

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, closed-world semantics, so the bar is lower. The description adds useful content-level context — the full Markdown body, provenance, and related ids are returned — which goes beyond the structured fields. It does not describe behavior for an unknown/missing id, a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with what the tool returns, followed by the routing condition. No filler and nothing repeated.

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 an output schema present, the description needn't detail return values, and annotations plus full schema coverage carry the rest. It is essentially complete for a simple single-fetch tool; only the missing-id/error case 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 description coverage is 100%, so both parameters (id, locale) are already fully documented, including the enum. The description's id/slug mention adds marginal value but mostly restates the schema; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (get) and resource (one Harness Engineering Handbook chapter), gives the id format example ('HRN-001') and slug alternative, and names itself as distinct from the list/search siblings. An agent can tell it apart from list_handbook or search without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use this once search or list_handbook has given you an id.' It names both alternative tools and the precise condition that selects this one, leaving little to inference.

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

All Santismm Knowledge — Harness Engineering, Agentic AI & Governance tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.