Skip to main content
Glama

Outil.io

List service connections

list_service_connections
Read-only

Connexions réelles du projet : Google Drive, Gmail, OneDrive, Outlook, Zoom et Calendly. Retourne connecté/configuré et compte, jamais les jetons. Connexion manquante : ouvrir /settings?tab=integrations ; l’utilisateur autorise le fournisseur. Les connexions SMTP, réseaux sociaux et IA se trouvent dans list_connections.

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_service_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and non-open-world, so the safety bar is low; the description still adds real value by stating what is returned (connected/configured status and account) and that tokens are never exposed, plus the human-in-the-loop authorization step. It does not cover pagination, ordering, or what an empty result looks like, which keeps it at 4 rather than 5.

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?

Four short sentences, front-loaded with scope and ending with the routing note to list_connections. The provider enumeration is slightly long but pays for itself by making scope concrete; nothing reads as filler.

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 read tool with no output schema, the description covers purpose, returned fields, secret handling, and the alternative tool. A little more on result shape (e.g. one entry per provider, ordering) would make it fully self-sufficient.

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 and there is nothing for the description to disambiguate. No parameter guidance is needed or given, and none is missing.

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 ('Connexions réelles du projet') and enumerates the providers it covers (Google Drive, Gmail, OneDrive, Outlook, Zoom, Calendly), which immediately separates it from generic connection listings. It also explicitly names the sibling that holds the other connection types, so an agent can route without opening either 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 when-to-use split: SMTP, social media and AI connections belong to list_connections, everything else here. It further supplies a concrete remediation path when a connection is missing (open /settings?tab=integrations and have the user authorize the provider), so both selection and follow-up action are covered.

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.