Skip to main content
Glama

list_clients

List every client and the providers each can reach, optionally verifying live sessions.

Instructions

List every client and which providers each can actually reach.

connected means the session opens right now, not that a credential is filed. Those are different facts, and reporting the second as the first is how two dead sessions read as connected for a day: nothing local can tell them apart, because OAuth grants a token and never says another word about it.

So this asks each provider, concurrently. Pass check=false to skip that and report only what is stored, which is instant and was the old behaviour.

stored is the union of two different things and says which is which. api_key is a pasted key, used by the REST adapters; mcp_session is an OAuth session, used by the provider's own tools. A provider can have one and not the other, which is how plan_mail_setup refused a client that client_status had just called connected. Neither list is a claim that the credential works: it is a claim that one is filed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkNoAsk each provider whether the session still opens. False reports only what is stored, which is instant.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / check / description
      Added value: +"Ask each provider whether the session still opens. False reports only what is stored, which is instant."
  2. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It explicitly discloses that the tool asks each provider concurrently by default, can skip that with check=false, and makes the distinction between actual connectivity and stored credential state.

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 stylistically repetitive in places but remains focused and understandable. It delivers the key behavioral points without excessive length.

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?

The description covers the main behavior and parameter semantics, and an output schema is present, so the lack of explicit return-value details is acceptable.

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 schema already documents check with 100% coverage, and the description adds meaningful context by explaining the trade-off between live checks and instant stored results.

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 clearly states the tool's primary purpose: listing every client and which providers each can actually reach. This distinguishes it from related sibling tools like find_across_clients by emphasizing the client-level listing scope.

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?

The description explains when to set check=false (to report stored state instantly) and clarifies the difference between live connectivity and stored credentials, giving the agent enough guidance to choose the right behavior.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsg42/munim'

If you have feedback or need assistance with the MCP directory API, please join our Discord server