Skip to main content
Glama

list_connections

Lists all connected sources with their status, tool counts, and reconnect links so you can verify account connections and repair any that need attention.

Instructions

List every connected source with status, tool count and the link to reconnect it.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does communicate useful behavior — it enumerates everything ("every"), and returns status, tool count, and a reconnect link — which implies a read-only, credential/integration-oriented operation. However, it never states that it is side-effect free, whether it requires authentication, or how the listing behaves at scale (no pagination hint), so a meaningful gap remains.

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 front-loaded sentence with no filler; the resource comes first and the returned fields follow. Nothing could be removed without losing information.

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?

For a zero-parameter tool with no output schema and no annotations, the description does explain what comes back (status, tool count, reconnect link), which is the main thing an agent needs. The residual gap is behavioral rather than structural: permissions and result size/pagination are unaddressed.

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 schema warrants a baseline of 4. The description correctly describes a no-argument, whole-collection listing and does not invent filtering semantics that the schema cannot 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 opens with a specific verb and resource ("List every connected source") and then names the payload fields (status, tool count, reconnect link), so the agent knows exactly what kind of result to expect. It does not explicitly differentiate itself from any sibling, but none of the listed siblings (search_tools, read_memory, execute, etc.) plausibly overlap with enumerating connected sources, so the omission costs little.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no when-not-to-use condition, and no named alternative. The agent must infer that this is the enumeration entry point for connected integrations, which is reasonable but left entirely implicit.

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