bharosa-docs-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bharosa_api_searchB | Search bundled API reference documents. Every result is documentation text, including references describing write endpoints. The optional method filter matches a documented HTTP verb; it does not send a request or select an action to execute. This tool only reads a local index and can never read or write an account. |
| bharosa_api_detailsA | Read one canonical API operation: method, path, parameters, body/responses and available source examples. Follow schema document IDs for referenced definitions. No API execution or credentials. |
| bharosa_examples_searchA | Find source-pinned SDK, cURL and guide examples by literal query, language or operation ID. Reports precise synthetic/typecheck/syntax validation scope; no live integration claim. |
| bharosa_examples_readA | Read a canonical example by allowlisted ID, its optional initialization context and source hash. UTF-16 offsets; at most 8000 code units. Returns text only; never executes code. |
| bharosa_docs_listA | List bundled public documentation. Offset is a document index; at most 20 results. No filesystem or network access from arguments. |
| bharosa_docs_searchA | Search bundled IDs, titles and text using case-insensitive literal AND terms, ranked by exact ID/title and title matches with source-order ties. At most 120 query characters and 20 results; no regex or remote search. |
| bharosa_docs_readA | Read bundled documentation by its allowlisted ID from bharosa_docs_list. Offset and maxChars count UTF-16 code units; at most 8000 per response. No path or URL input. |
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 7 tools
The set splits cleanly into three resource families (api, examples, docs), each with search/read-style operations, so most tools are easy to tell apart. The main soft spot is bharosa_api_search vs bharosa_docs_search, since API reference pages are arguably also bundled docs; the descriptions clarify the difference (API operations vs general doc index) but an agent could still hesitate.
All tools share a predictable bharosa_<resource>_<action> pattern with snake_case throughout. The only deviation is bharosa_api_details, which uses a noun ('details') instead of a verb like read/get, breaking the otherwise uniform verb convention.
Seven tools is well-scoped for a read-only documentation server, with each tool earning its place across three resource families. Nothing feels padded or missing at the count level.
Docs have list/search/read, examples have search/read, and API operations have search/details, covering the core read-only lifecycle. Minor gaps: there is no way to enumerate API operations or list examples directly (only search), so discovery depends on guessing good queries.