Skip to main content
Glama

ActionDock

by app.actiondock
OverviewDiscussionsAdmin

List connections

list_connections
Read-onlyIdempotent

List the workspace-approved HTTPS API connections, method/path allowlists and public operator identification with the effective User-Agent. Credentials are never returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionsYesWorkspace-approved API connections with method/path allowlists, operatorIdentity and userAgent; credentials are never included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / connections / description
      Previous value: -"Workspace-approved API connections with their method and path allowlists; credentials are never included."New value: +"Workspace-approved API connections with method/path allowlists, operatorIdentity and userAgent; credentials are never included."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "connections": {
+      "description": "Workspace-approved API connections with their method and path allowlists; credentials are never included.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "connections"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower, and the description still adds genuinely useful behavioral facts: results are scoped to 'workspace-approved' connections and 'Credentials are never returned'. The credential non-disclosure is exactly the kind of security context annotations cannot convey. It stops short of describing result size or ordering.

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?

A single dense sentence that front-loads the action and resource, then lists the returned fields and closes with the credential-safety guarantee. No filler and nothing that could be trimmed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be spelled out, yet the description still orients the agent on scope (workspace-approved), content categories and the credential exclusion. For a zero-parameter read-only tool with full annotation coverage, nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-related to clarify and the description correctly avoids inventing filter semantics that the empty schema does not support.

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?

The description names a specific verb and resource ('List the workspace-approved HTTPS API connections') and enumerates what is returned (method/path allowlists, operator identification, effective User-Agent). The resource is distinct enough from siblings like list_actions, list_events and list_usage that no explicit sibling disambiguation is needed, though it never names an alternative.

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?

There is no explicit when-to-use or when-not-to-use statement. Usage is implied by the listing semantics and by the resource name, which is adequate for a zero-parameter read-only lister, but the description offers no routing guidance against the other list_* siblings.

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

All ActionDock toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources