Skip to main content
Glama

list_providers

Check which LLM providers are available and whether each is logged in, returning an error code for any provider that is not authenticated.

Instructions

Providers and whether each is logged in (error code if not).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 burden, and it does disclose the return content: per-provider login status plus an error code when a provider is not logged in. It does not say whether the call performs live auth checks, is read-only and side-effect free, or whether the error codes come from a prior attempt, leaving meaningful behavioral gaps for an unannotated tool.

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?

A single short sentence with the core content (providers, login state) front-loaded and the parenthetical adding genuinely useful detail about the failure case. No filler, though the phrasing is clipped enough that 'Providers' reads ambiguously as a noun fragment.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, the description does need to convey the return shape, and it does so only at a high level — it does not indicate what a provider identifier looks like or what fields accompany the login flag, which matters if the agent must pass one to 'login'. Adequate but thin for a tool whose output the agent must act on.

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 there is no parameter meaning to convey and no schema gap to compensate for. Baseline 4 applies.

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 names the resource (providers) and the attribute returned for each (login status, with an error code when not logged in), so an agent can tell this is a status-listing tool rather than an authentication action. It implicitly contrasts with the sibling 'login', but never states that contrast explicitly and omits a verb like 'list'.

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 guidance on when to call this versus the 'login' sibling, no prerequisites, and no note on whether it should be used to check auth state before invoking login. The agent must infer the call context entirely.

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