Skip to main content
Glama

Search the Body of Knowledge

search_bok
Read-onlyIdempotent

Search the 24 chapters of the AI Governance Engineer Body of Knowledge and its pattern pages: chapter titles, summaries and key points, section headings and section text. Every query word must match. Returns chapters, sections (with the URL of the heading anchor) and patterns, best first, each with a snippet. Use it to find where the book treats a subject ("human oversight", "post-market monitoring", "agent identity", "conformity assessment").

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

Input Schema

NameRequiredDescriptionDefault
kindNoRestrict the result type.any
limitNoMaximum number of results.
queryYesWords to look for.

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
datasetYesURL of the open-data document the answer was read from.
licenseYesLicence of the data (CC BY 4.0, attribution required).
resultsYes
dataVersionYesBody of Knowledge version of the data.
headingsSearchedYesFalse when the chapter text was unavailable and only chapters.json was searched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, destructive=false, closed-world), and the description adds genuinely new behavior: strict conjunctive matching ('Every query word must match'), best-first ranking, per-result snippets, and heading-anchor URLs for sections. It stops short of describing empty-result behavior or how ranking works, so not a 5.

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?

Two sentences, scope first, then usage examples — front-loaded and free of filler. The list of searched fields is long but each item carries information an agent uses to predict recall.

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 three-parameter search tool with an output schema and full schema coverage, the description supplies the missing pieces: search scope, matching rule, result shape, ordering, and use case. Nothing needed to call it correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the AND semantics of the query (schema only says 'Words to look for') and the fact that results come back as chapters, sections, or patterns, which clarifies the `kind` enum's practical effect.

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 (Search) plus the exact resource (the 24-chapter AI Governance Engineer Body of Knowledge and its pattern pages) and even enumerates the searched fields (chapter titles, summaries, key points, section headings and text). An agent can immediately distinguish this full-text book search from glossary/term lookup siblings.

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

Usage Guidelines4/5

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

Gives clear when-to-use framing — 'Use it to find where the book treats a subject' — with four concrete example queries ("human oversight", "post-market monitoring", "agent identity", "conformity assessment"). It does not explicitly exclude alternatives such as search_glossary or get_pattern, so it falls short of the 5 bar.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.