Skip to main content
Glama

List connections

list_connections
Read-onlyIdempotent

Lists available filesystem or SharePoint storage connections and their capabilities, so you can use the correct connectionId for registering and editing documents.

Instructions

List the connections you can address documents under. Returns [{connectionId, provider, canCreateDocuments, allowedExtensions, defaultChangeMode, defaultChangeGranularity, calculatesFormulas, listable, templatesFolder, templateLocation, readOnly}] where provider names the storage, such as "filesystem" or "sharepoint"; listable says list_documents works on it, templateLocation (organization, workgroup, personal, connection, or null) says it holds templates, and readOnly true means it is never written to. Use a connectionId as the connectionId for register_document and the document tools; never ask the user for 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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so safety is covered. The description adds genuinely non-obvious semantics: readOnly means it is never written to, listable gates list_documents, and templateLocation enumerates its possible values — context not derivable from annotations.

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?

Purpose is front-loaded and every clause carries information, but the middle section is a single dense run-on listing eleven fields, which is harder to scan than a short bulleted mapping. No wasted words, though.

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?

With no output schema, the description correctly carries the return contract by naming the shape and explaining the non-obvious fields. It stops short of covering edge cases such as an empty connection list or ordering, which for a zero-arg discovery tool is a minor gap.

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?

Zero parameters, so there is nothing to disambiguate and the baseline applies. The description instead spends its space on return-field semantics, which is the right allocation for a no-arg tool.

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?

States a specific verb and resource ('List the connections you can address documents under') and scopes the resource as document-addressable storage backends, which separates it from list_documents and find_templates. It does not explicitly name a sibling it replaces, but the resource is unambiguous.

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

Usage Guidelines4/5

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

Clearly implies this is the discovery step that produces a connectionId, and instructs the agent to feed that value into register_document and the document tools rather than asking the user. It lacks an explicit 'call this before X' ordering statement, but the downstream routing is spelled out.

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