Skip to main content
Glama

List connections

list_connections
Read-onlyIdempotent

List workspace-approved HTTPS connections, enabled state, allowed methods and path rules. GET /records/ permits that method under the prefix; PATCH =/records/42 permits only that exact method and path. The method must also be enabled. Rules without a method apply to every enabled method. Submit only the path, without the method or = marker. Also returns public operator identification and the effective User-Agent. Credentials are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
connectionsYesWorkspace-approved API connections with enabled state (false means paused; only the owner can resume), 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 method/path allowlists, operatorIdentity and userAgent; credentials are never included."New value: +"Workspace-approved API connections with enabled state (false means paused; only the owner can resume), method/path allowlists, operatorIdentity and userAgent; credentials are never included."
  2. 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."
  3. 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"
      +}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral detail beyond that: it explains the path-rule matching semantics, says public operator identification and the effective User-Agent are returned, and explicitly states that credentials are never returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and reasonably efficient, with the purpose stated first. The middle sentences about rule syntax are relevant for interpreting returned connections, but the final "Submit only the path" instruction does not earn its place in a listing tool.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a zero-parameter read-only tool with an output schema, the description is mostly complete: it covers what is returned, explains how path rules should be read, and notes that credentials are excluded. The stray instruction to "submit" a path slightly undermines completeness because the tool has no input fields.

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

Parameters3/5

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

There are zero input parameters, so the baseline is 4. However, the description includes "Submit only the path, without the method or = marker," which is confusing for a zero-parameter list tool and may imply an input that the schema does not contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description begins with a specific verb and resource: "List workspace-approved HTTPS connections, enabled state, allowed methods and path rules." That is enough for an agent to identify the operation and its scope without needing sibling names.

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?

Usage is implied by the name and description, but there is no explicit when-to-use guidance, no exclusions, and no comparison with alternatives. An agent can infer that this is the inspection tool for connections, but the definition does not route it against alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources