B2Bizzio 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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_infoC | Get information about B2Bizzio services |
| echoB | Echo a message back to the user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| business_analysis | Generate a business analysis prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| welcome | Welcome message for B2Bizzio MCP server |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: get_info retrieves service information, while echo simply returns a message. There is no overlap or ambiguity between them.
Both names are lowercase verbs, but get_info follows a verb_noun pattern with an underscore, while echo is just a bare verb. The naming is mostly consistent but shows a minor stylistic deviation.
With only two tools, the server feels thin and minimal. The count is borderline acceptable for a very focused utility, but it may be insufficient for a full-featured service.
The domain appears to be B2Bizzio services, but only get_info is relevant to that domain, and echo is an unrelated utility. There are no create, update, delete, or other operational tools, making the surface severely incomplete.