Skip to main content
Glama

list_providers

Read-onlyIdempotent

List workspace-scoped provider instances and their limits, status, and slugs. Use this to find provider slugs for workspace-level updates.

Instructions

List workspace-scoped provider instances and their limits or status. Use this to find provider slugs for workspace-level updates; use list_integrations for the org-level source connection. Returns total plus provider name, slug, integration, status, limits, expiration, and reset flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
current_pageNoPage number for pagination
page_sizeNoNumber of results per page (max 100, default 50)
workspace_idNoWorkspace ID - required when using organization admin keys, optional with workspace API keys

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Implementation Reference

  • The MCP tool handler for 'list_providers'. It calls service.providers.listProviders(), then maps the response to a JSON text result containing total, provider name, slug, integration_id, status, note, usage_limits, rate_limits, reset_usage, expires_at, and created_at.
    server.tool(
    	"list_providers",
    	"List workspace-scoped provider instances and their limits or status. Use this to find provider slugs for workspace-level updates; use list_integrations for the org-level source connection. Returns total plus provider name, slug, integration, status, limits, expiration, and reset flags.",
    	PROVIDERS_TOOL_SCHEMAS.listProviders,
    	async (params) => {
    		const providers = await service.providers.listProviders({
    			current_page: params.current_page,
    			page_size: params.page_size,
    			workspace_id: params.workspace_id,
    		});
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(
    						{
    							total: providers.total,
    							providers: providers.data.map((provider) => ({
    								name: provider.name,
    								slug: provider.slug,
    								integration_id: provider.integration_id,
    								status: provider.status,
    								note: provider.note,
    								usage_limits: provider.usage_limits
    									? {
    											credit_limit: provider.usage_limits.credit_limit,
    											alert_threshold: provider.usage_limits.alert_threshold,
    											periodic_reset: provider.usage_limits.periodic_reset,
    										}
    									: null,
    								rate_limits:
    									provider.rate_limits?.map((limit) => ({
    										type: limit.type,
    										unit: limit.unit,
    										value: limit.value,
    									})) ?? null,
    								reset_usage: provider.reset_usage,
    								expires_at: provider.expires_at,
    								created_at: provider.created_at,
    							})),
    						},
    						null,
    						2,
    					),
    				},
    			],
    		};
    	},
    );
  • Zod input schema for list_providers: optional current_page (positive number), page_size (int, 1-100), and workspace_id (string).
    listProviders: {
    	current_page: z.coerce
    		.number()
    		.positive()
    		.optional()
    		.describe("Page number for pagination"),
    	page_size: z.coerce
    		.number()
    		.int()
    		.positive()
    		.max(100)
    		.optional()
    		.describe("Number of results per page (max 100, default 50)"),
    	workspace_id: z
    		.string()
    		.optional()
    		.describe(
    			"Workspace ID - required when using organization admin keys, optional with workspace API keys",
    		),
    },
  • Service method 'listProviders' that sends a GET request to '/providers' with optional params (current_page, page_size, workspace_id), returning a ListProvidersResponse.
    export class ProvidersService extends BaseService {
    	async listProviders(
    		params?: ListProvidersParams,
    	): Promise<ListProvidersResponse> {
    		return this.get<ListProvidersResponse>("/providers", params);
  • Type definitions for ListProvidersResponse (object, total, data: Provider[]) and ListProvidersParams (current_page?, page_size?, workspace_id?).
    export interface ListProvidersResponse {
    	object: "list";
    	total: number;
    	data: Provider[];
    }
    
    export interface ListProvidersParams {
    	current_page?: number;
    	page_size?: number;
    	workspace_id?: string;
    }
  • The 'providers' domain is registered in TOOL_DOMAIN_REGISTRARS at line 45, mapping to registerProvidersTools, which is called by registerAllTools to wire up the list_providers tool on the MCP server.
    const TOOL_DOMAIN_REGISTRARS = [
    	["users", registerUsersTools],
    	["workspaces", registerWorkspacesTools],
    	["configs", registerConfigsTools],
    	["keys", registerKeysTools],
    	["collections", registerCollectionsTools],
    	["prompts", registerPromptsTools],
    	["analytics", registerAnalyticsTools],
    	["guardrails", registerGuardrailsTools],
    	["limits", registerLimitsTools],
    	["audit", registerAuditTools],
    	["labels", registerLabelsTools],
    	["partials", registerPartialsTools],
    	["tracing", registerTracingTools],
    	["logging", registerLoggingTools],
    	["providers", registerProvidersTools],
    	["integrations", registerIntegrationsTools],
    	["mcp-integrations", registerMcpIntegrationsTools],
    	["mcp-servers", registerMcpServersTools],
    ] as const satisfies readonly (readonly [string, ToolRegistrar])[];
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds value by specifying output fields (name, slug, etc.) and scope (workspace-scoped). No contradictions.

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?

Two sentences with no waste. First sentence states core functionality and scope, second sentence provides usage context and output summary. Information is front-loaded and efficient.

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?

With output schema existing, the description adequately covers purpose, scope, usage guidance, and output fields. No gaps for a listing tool. Pagination is handled by schema.

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?

Schema coverage is 100% with clear parameter descriptions. The description does not add additional parameter meaning beyond the schema, so baseline 3 is appropriate.

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 verb 'list', the resource 'workspace-scoped provider instances', and what is included (limits/status). It also distinguishes from sibling tool list_integrations, making purpose unambiguous.

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?

Explicitly says to use for workspace-level updates and to use list_integrations for org-level connections. Provides clear when-to-use and when-not-to-use guidance with a named alternative.

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

Install Server

Other Tools

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/s-b-e-n-s-o-n/portkey-admin-mcp'

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