Broadcom Support MCP Server
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationB | Search the Broadcom Support knowledge base for articles matching the query. Returns a list of relevant articles with titles, URLs, and snippets. |
| read_documentationB | Retrieve the full content of a Broadcom Support article at the given URL. Returns the article title, body text, and metadata. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a specific article by URL, while the other searches the knowledge base with a query. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (read_documentation, search_documentation), using the same naming convention and clear, descriptive verbs.
With only two tools, the server feels thin for a support knowledge base domain. While the tools cover basic retrieval and search, typical support systems might benefit from additional operations like filtering by category, viewing recent articles, or handling user authentication.
The tools provide core read and search functionality, but there are notable gaps. For example, there is no way to browse articles by category, list trending or recent content, or manage user-specific features like saved articles or subscriptions, which could limit agent workflows.