Skip to main content
Glama

list_mcp_server_connections

Read-onlyIdempotent

List active connection records for a Portkey-managed MCP server, including user, connected state, and timestamps, to audit sessions or identify which user to disconnect.

Instructions

List active connection records for one Portkey-managed MCP server, including user, connected state, and connection timestamps. Use it to audit sessions or identify the user/workspace before disconnect_mcp_server_connection; service keys can list all users, while user keys default to their own user. Organisation admin keys must provide workspace_id. This reads live connection state and does not test upstream server reachability (use test_mcp_server for that).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesMCP server ID or slug whose connections to list
user_idNoUser UUID to filter; user-scoped keys default to their own user when omitted
page_sizeNoConnections per page, from 1 through 500; defaults to 100
current_pageNoZero-based results page; defaults to 0
workspace_idNoWorkspace ID or slug; required with an organisation admin API key

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changedv0.11.5
    • addedInput schema / properties / page_size / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / page_size / minimum
      Removed value: -1
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), and the description still adds non-obvious behavior: key-type-dependent scoping (service keys see all users, user keys self-scope, org admin keys must pass workspace_id) and the boundary that it reads live state without probing the upstream server. Those are permission and scope semantics an agent cannot infer from the annotations.

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?

Front-loads what is listed and its scope in the first sentence, then usage, then access rules, then the exclusion. Every clause carries distinct information; nothing is decorative.

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?

For a read-only, 5-parameter tool with an output schema and full annotation coverage, the description supplies the missing pieces (key-type scoping, sibling routing, reachability boundary) without redundantly explaining return values.

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?

With 100% schema description coverage, the schema already documents id, user_id, workspace_id, page_size, and current_page including defaults and bounds. The description's key-scoping notes largely restate what the schema descriptions already say, so it adds little beyond the structured baseline.

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?

States a specific verb and resource ('List active connection records for one Portkey-managed MCP server') and enumerates the returned fields (user, connected state, timestamps), which lets an agent distinguish it from get_mcp_server or list_mcp_server_user_access without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('audit sessions or identify the user/workspace before disconnect_mcp_server_connection') and an explicit exclusion with the correct alternative ('does not test upstream server reachability (use test_mcp_server for that)'). This is the when-to-use / when-not-to-use / alternative pattern at full strength.

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

Deploy Server

Other Tools