Skip to main content
Glama
bharosa-docs-mcp

bharosa-docs-mcp

by bhafin

Search Bharosa Documentation

bharosa_docs_search
Read-onlyIdempotent

Searches bundled Bharosa documentation by case-insensitive literal keywords, ranking exact ID and title matches to help coding agents find API operation details and SDK/cURL examples.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
totalYes
noticeYes
matchesYes
reviewedOnYes
availabilityYes
bundleVersionYes
checkpointDateYes
contractVersionYes
contractSourcePathYes
contractSourceSha256Yes
publicContractSha256Yes
publicContractVersionYes
approvedManifestSha256Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.7
    • changedOutput schema / properties / bundleVersion / const
      Previous value: -"0.3.6-docs.1"New value: +"0.3.7-docs.1"
    • changedOutput schema / properties / matches / items / properties / sourcePath / enum
      Previous value: -[
      -  "marketing/src/content/guides.ts",
      -  "marketing/src/content/analytics-guides.ts",
      -  "marketing/src/content/benchmark-guide.ts",
      -  "sdk/test/openapi.json",
      -  "sdk/test/analytics.openapi.json",
      -  "sdk/test/market-search.openapi.json",
      -  "sdk/test/baseline-market.openapi.json",
      -  "sdk/test/fund-aum.openapi.json",
      -  "sdk/test/benchmarks.openapi.json",
      -  "marketing/src/content/consent-guide.ts"
      -]New value: +[
      +  "marketing/src/content/guides.ts",
      +  "marketing/src/content/analytics-guides.ts",
      +  "marketing/src/content/benchmark-guide.ts",
      +  "sdk/test/openapi.json",
      +  "sdk/test/analytics.openapi.json",
      +  "sdk/test/market-search.openapi.json",
      +  "sdk/test/baseline-market.openapi.json",
      +  "sdk/test/fund-aum.openapi.json",
      +  "sdk/test/benchmarks.openapi.json",
      +  "sdk/test/catalog.openapi.json",
      +  "marketing/src/content/catalog-v010.ts",
      +  "marketing/src/content/consent-guide.ts"
      +]
  2. Changed2 schema fields changedv0.3.6
    • changedOutput schema / properties / bundleVersion / const
      Previous value: -"0.3.2-docs.1"New value: +"0.3.6-docs.1"
    • changedOutput schema / properties / matches / items / properties / sourcePath / enum
      Previous value: -[
      -  "marketing/src/content/guides.ts",
      -  "marketing/src/content/analytics-guides.ts",
      -  "sdk/test/openapi.json",
      -  "sdk/test/analytics.openapi.json",
      -  "sdk/test/market-search.openapi.json",
      -  "marketing/src/content/consent-guide.ts"
      -]New value: +[
      +  "marketing/src/content/guides.ts",
      +  "marketing/src/content/analytics-guides.ts",
      +  "marketing/src/content/benchmark-guide.ts",
      +  "sdk/test/openapi.json",
      +  "sdk/test/analytics.openapi.json",
      +  "sdk/test/market-search.openapi.json",
      +  "sdk/test/baseline-market.openapi.json",
      +  "sdk/test/fund-aum.openapi.json",
      +  "sdk/test/benchmarks.openapi.json",
      +  "marketing/src/content/consent-guide.ts"
      +]
  3. Changed2 schema fields changedv0.3.2
    • changedOutput schema / properties / bundleVersion / const
      Previous value: -"0.2.0-docs.1"New value: +"0.3.2-docs.1"
    • changedOutput schema / properties / matches / items / properties / sourcePath / enum
      Previous value: -[
      -  "marketing/src/content/guides.ts",
      -  "marketing/contracts/openapi.json"
      -]New value: +[
      +  "marketing/src/content/guides.ts",
      +  "marketing/src/content/analytics-guides.ts",
      +  "sdk/test/openapi.json",
      +  "sdk/test/analytics.openapi.json",
      +  "sdk/test/market-search.openapi.json",
      +  "marketing/src/content/consent-guide.ts"
      +]
  4. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful search semantics beyond annotations: case-insensitive literal AND matching, ranking by exact ID/title and title matches, source-order ties, and hard limits.

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 compact and front-loaded, packing search behavior, ranking, and constraints into one dense sentence with no filler.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. It supplies the key search semantics and constraints, with only minor omissions around default limit behavior.

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 0%, so the description must compensate. It explains that query terms are case-insensitive literal AND terms capped at 120 characters and that results are capped at 20, but it omits the default limit of 5 and the minimum value of 1.

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

Purpose4/5

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

States a specific verb, "Search," and a specific resource, "bundled IDs, titles and text." The purpose is clear, though it does not explicitly differentiate itself from sibling tools such as bharosa_docs_list or bharosa_examples_search.

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

Usage Guidelines3/5

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

Provides useful constraints such as no regex or remote search and result/query limits, which imply appropriate usage. However, it does not explicitly say when to use this tool instead of bharosa_docs_list, bharosa_docs_read, or bharosa_examples_search.

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