Skip to main content
Glama
santismm

santismm-knowledge

Official
by santismm
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get a Harness Engineering Handbook Chapter

get_handbook
Read-onlyIdempotent

Retrieve a Harness Engineering Handbook chapter by id or slug to get its full Markdown body, provenance, and related ids. Use it after searching or listing to access specific content.

Instructions

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
NameRequiredDescriptionDefault
idYesChapter id like 'HRN-001', or its slug.
localeNoLanguage of the returned body. Default: en.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bodyNoFull Markdown body of the chapter.
nameNo
slugNo
tagsNo
domainNo
localeNo
statusNo
aliasesNo
api_urlNo
localesNo
relatedNo
summaryNo
updatedNo
versionNo
categoryNo
evidenceNoEvidence-First provenance: weight claims by this.
fallbackNoTrue when the body is not in the requested locale.
featuredNo
patternsNo
knowledgeNo
frameworksNo
referencesNo
resource_uriNo
technologiesNo
canonical_urlNo
resolved_localeNoThe 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_localeNoThe locale that was asked for.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.4.1
    • addedInput schema / properties / id / maxLength
      Added value: +128
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedOutput schema / properties / aliases
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / resolved_locale / description
      Previous value: -"The locale actually returned — the handbook is authored in English only."New value: +"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."
    • addedOutput schema / properties / resource_uri
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail by stating that the tool 'Returns the full Markdown body plus its provenance and related ids,' which is not evident from the annotations alone.

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?

The description is two sentences with no filler. The core action and distinguishing lookup-by-id behavior are front-loaded, and the usage guidance is included without redundant detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity read-only tool with a full input schema, safety annotations, and an output schema, the description is complete. It explains what the tool returns, how to identify a chapter, and when to use it, leaving no critical gap for an agent to call it correctly.

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%, and both the id and locale parameters already include descriptive text, including the id-or-slug semantics and the 'Default: en' for locale. The description reinforces this but adds little beyond what the schema provides, so a 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?

The description states a specific verb and resource: 'Get one Harness Engineering Handbook chapter,' and clarifies lookup by 'id (e.g. 'HRN-001') or slug.' It is clearly distinct from sibling listing tools like list_handbook and search_all.

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?

The description gives explicit usage guidance: 'Use this once search or list_handbook has given you an id.' This tells an agent that this tool is for retrieval after discovery, not for browsing or searching, and names the tools that should be used first.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/santismm/santismm-knowledge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server