Skip to main content
Glama
bharosa-docs-mcp

bharosa-docs-mcp

by bhafin

List Bharosa Documentation

bharosa_docs_list
Read-onlyIdempotent

Lists bundled public documentation with pagination so coding agents can discover available Bharosa docs without filesystem or network access.

Instructions

List bundled public documentation. Offset is a document index; at most 20 results. No filesystem or network access from arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bharosa_docs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
totalYes
noticeYes
documentsYes
nextOffsetYes
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 / documents / 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. Changed3 schema fields changedv0.3.6
    • changedInput schema / properties / offset / maximum
      Previous value: -128New value: +192
    • changedOutput schema / properties / bundleVersion / const
      Previous value: -"0.3.2-docs.1"New value: +"0.3.6-docs.1"
    • changedOutput schema / properties / documents / 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 / documents / 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.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower; the description still adds real substance by disclosing the 20-result ceiling and clarifying that offset is a document index rather than a byte offset. The explicit "no filesystem or network access from arguments" note usefully rules out path/injection-style argument behavior that annotations alone would not convey.

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?

Three short sentences, front-loaded with the purpose, then pagination semantics, then the safety constraint. No filler, though the final sentence is a defensive caveat that reads as bolted-on rather than integrated with the offset explanation.

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 only two optional parameters, a real output schema (so return values needn't be described) and full annotation coverage, the description supplies what an agent needs to page through the index safely. The remaining gap is minor: defaults for limit/offset are left to the schema.

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 carries the burden and does partially compensate by defining offset as a document index and tying the 20-result cap to the limit maximum. It leaves the default of 10, the minimum of 1, and the offset ceiling of 192 unexplained, so the schema still holds undisclosed meaning.

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?

"List bundled public documentation" gives a specific verb (list/enumerate) plus the resource (bundled docs), which distinguishes it from the read/search siblings by implication of enumeration rather than lookup. It stops short of naming the sibling tools, but the operation is unambiguous.

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?

The description implies browsing the documentation index and notes the 20-result cap, which hints at paging through results, but it neither states when to prefer this over bharosa_docs_search/read nor gives any exclusions. A caller can infer the use case but is given no explicit routing guidance.

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