Skip to main content
Glama
vishalsg42

munim

by vishalsg42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_clients

List every client with stored credentials and live connection status across providers. Set check=false to skip live probes and get an instant report of what's stored.

Instructions

List every client and what each one can actually reach.

Returns one row per client with their domain, stored (every provider with a credential filed), api_key and mcp_session saying which store each came from, and connected, needs_login and unreachable from asking each provider live. Pass check=false to skip the live probes and report only what is stored, which is instant.

Use client_status for one client in the same shape.

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.

  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 provided, the description carries the full burden of disclosing behavior. It explains that the tool performs live provider probes, can be short-circuited with check=false, and returns a mix of stored and live status fields. This is substantive behavioral context beyond the tool name.

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?

Every sentence earns its place: the core purpose, the return shape, the optional parameter behavior, and the sibling alternative. The description is well-structured, front-loaded, and free of filler.

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?

Given the output schema exists and there is only one optional parameter, the description fully covers what the agent needs: scope, return semantics, live vs. stored modes, and the single-client alternative. Nothing important is missing.

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?

The input schema already fully documents the check parameter with 100% coverage, so the baseline is 3. The description restates the same behavior without adding new semantic meaning beyond what the schema already provides.

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 opens with a specific verb and resource: 'List every client and what each one can actually reach.' It immediately differentiates itself from the sibling client_status, so an agent can tell exactly what this tool does without opening the schema.

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?

It explicitly directs the agent to use client_status for a single client and explains the behavioral choice between live checks and check=false. It does not discuss every sibling alternative, but it gives clear routing for the most relevant one.

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