get_connection_configGet MCP setup instructions for connecting to Pipeworx packs. Returns connection details and gateway URLs. Use to configure your environment.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes | Comma-separated pack slugs (e.g., "weather,github,jokes") or "all" for everything |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "oneOf": [
+ {
+ "description": "Configuration for all packs",
+ "properties": {
+ "claude_code": {
+ "description": "Claude Code CLI command",
+ "type": "string"
+ },
+ "claude_desktop": {
+ "properties": {
+ "mcpServers": {
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "endpoint": {
+ "description": "MCP endpoint URL",
+ "type": "string"
+ },
+ "note": {
+ "description": "Configuration note",
+ "type": "string"
+ }
+ },
+ "required": [
+ "note",
+ "claude_desktop",
+ "claude_code",
+ "endpoint"
+ ],
+ "type": "object"
+ },
+ {
+ "description": "Configuration for specific packs",
+ "properties": {
+ "claude_code": {
+ "description": "Claude Code CLI commands",
+ "type": "string"
+ },
+ "claude_desktop": {
+ "properties": {
+ "mcpServers": {
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "endpoints": {
+ "description": "MCP endpoint URLs",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "claude_desktop",
+ "claude_code",
+ "endpoints"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "slugs": "pipeworx-catalog"
+ },
+ {
+ "slugs": "weather,github,jokes"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds that it returns 'connection details and gateway URLs', which is minor behavioral context. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, no fluff, front-loaded with the key action and result. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, output schema present, annotations rich), the description fully covers its purpose and use. No need for more detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers the single parameter 'slugs' with a complete description including examples. Description does not add any additional parameter-specific meaning, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Get MCP setup instructions for connecting to Pipeworx packs' with specific verb 'Get' and resource 'connection config'. It distinguishes from sibling tools like search_packs or list_packs by focusing on setup instructions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use to configure your environment', providing clear context for when to use. However, does not mention when not to use or name alternative tools, but given its simple nature, this is acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.