dbconvert-streams
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dbconvert_get_connectionA | Get credential-free details for one connection: host, port, username, default database, SSL/SSH topology, cloud provider. Passwords, SSH private keys, and cloud access keys/tokens are never included — they are structurally absent, not redacted, so there is no way to retrieve them through MCP. Report only the fields present in the response. |
| dbconvert_list_data_sourcesA | List DBConvert Streams connections. Each item has exactly id, name, type, and (optionally) cloudProvider — nothing else. For host/port/username and other connection details use get_connection. Passwords and cloud keys are never exposed by any tool. Report connections using only the fields present; do not add invented fields like used_for or row_counts. |
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 complementary, non-overlapping roles: one lists connection summaries with basic metadata, and the other fetches detailed connection information. The descriptions explicitly cross-reference each other, so an agent should not confuse them.
Both tools follow the same dbconvert_<verb>_<noun> snake_case pattern (get_connection, list_data_sources), making the action and resource predictable and consistent.
Two tools is below the typical well-scoped range; while they cover a narrow read-only lookup use case cleanly, the surface feels thin for a product named DBConvert Streams and offers no operations beyond listing and inspecting connections.
The read-only connection metadata workflow (list then get detail) is covered, but the tool set omits connection lifecycle operations and any stream-related tools, so agents with broader management tasks will hit dead ends.