Skip to main content
Glama
bharosa-docs-mcp

bharosa-docs-mcp

by bhafin

Search Bharosa Code Examples

bharosa_examples_search
Read-onlyIdempotent

Find source-pinned SDK, cURL, and guide examples by literal query, language, or operation ID. Returns validation scope only, with no live integration claim.

Instructions

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.

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_examples_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesRequired nonblank literal search text, even when using language or operationId filters. Use the operation ID as query to find its examples. Maximum 120 raw characters.
languageNo
operationIdNo

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / codingVersion / const
      Previous value: -"0.3.6-coding.1"New value: +"0.3.7-coding.1"
    • changedOutput schema / properties / matches / items / properties / sdkVersion / const
      Previous value: -"0.9.0"New value: +"0.10.0"
    • changedOutput schema / properties / sdkVersion / const
      Previous value: -"0.9.0"New value: +"0.10.0"
  2. Changed4 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 / codingVersion / const
      Previous value: -"0.3.2-coding.1"New value: +"0.3.6-coding.1"
    • changedOutput schema / properties / matches / items / properties / sdkVersion / const
      Previous value: -"0.6.0"New value: +"0.9.0"
    • changedOutput schema / properties / sdkVersion / const
      Previous value: -"0.6.0"New value: +"0.9.0"
  3. Changed8 schema fields changedv0.3.2
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "typescript",
      -  "bash",
      -  "json"
      -]New value: +[
      +  "typescript",
      +  "javascript",
      +  "bash",
      +  "json"
      +]
    • addedInput schema / properties / query / description
      Added value: +"Required nonblank literal search text, even when using language or operationId filters. Use the operation ID as query to find its examples. Maximum 120 raw characters."
    • changedOutput schema / properties / bundleVersion / const
      Previous value: -"0.2.0-docs.1"New value: +"0.3.2-docs.1"
    • changedOutput schema / properties / codingVersion / const
      Previous value: -"0.2.0-coding.1"New value: +"0.3.2-coding.1"
    • changedOutput schema / properties / matches / items / properties / language / enum
      Previous value: -[
      -  "typescript",
      -  "bash",
      -  "json"
      -]New value: +[
      +  "typescript",
      +  "javascript",
      +  "bash",
      +  "json"
      +]
    • changedOutput schema / properties / matches / items / properties / sdkVersion / const
      Previous value: -"0.1.0"New value: +"0.6.0"
    • changedOutput schema / properties / matches / items / properties / validation / enum
      Previous value: -[
      -  "strict-typescript-and-synthetic-transport",
      -  "strict-typescript",
      -  "shell-syntax-only",
      -  "json-parse"
      -]New value: +[
      +  "strict-typescript-and-synthetic-transport",
      +  "strict-typescript",
      +  "shell-syntax-only",
      +  "javascript-syntax-only",
      +  "json-parse"
      +]
    • changedOutput schema / properties / sdkVersion / const
      Previous value: -"0.1.0"New value: +"0.6.0"
  4. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description still adds real value the annotations cannot: "source-pinned" and the disclaimer that validation scope is synthetic/typecheck/syntax only with "no live integration claim" is exactly the kind of caveat an agent needs before trusting returned code.

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?

Two sentences, no filler, and the retrieval model is front-loaded ahead of the validation-scope caveat. Every clause carries information an agent can act on.

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, so return shape needn't be described, and the caveat about validation scope covers the biggest trust question for a code-example tool. The remaining gap is the undocumented limit parameter and the missing sibling-routing note, which keeps it short of a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% – only query is documented in the schema, while language, limit and operationId carry nothing. The description restates the three filter axes but adds no semantics for them (accepted values, whether language filters out other-language examples, default/cap behavior) and never mentions limit at all, so it does not compensate for the coverage gap.

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?

"Find source-pinned SDK, cURL and guide examples" gives a specific verb plus a well-scoped resource, and the query/language/operationId axes make the retrieval model clear. It implicitly separates itself from the docs and API search siblings by naming the resource 'examples', but it never names those siblings explicitly.

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?

Usage is implied: search examples when you want runnable code rather than documentation prose. There is no explicit statement of when to prefer this over bharosa_docs_search or bharosa_api_search, and no exclusion guidance, so the agent must infer the routing decision.

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