Skip to main content
Glama

list_providers

Lists registered subagent providers with availability and capabilities, including tool execution and permission scope, so you can select a compatible provider.

Instructions

登録済みプロバイダーと利用可否・機能(ツール実行・権限範囲など)を返す

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 observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. The verb '返す' (returns) implies a harmless read, and it discloses that availability and feature information (tool execution, permission scope) are part of the payload, which is real behavioral context. However, it says nothing about pagination, ordering, or the concrete shape of the result, and the closing 'など' leaves the payload open-ended.

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?

A single front-loaded sentence with no filler; the resource comes first and the informative payload follows. Nothing redundant is present.

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 read-only listing tool this is close to adequate, and the absence of an output schema means a little more return-shape detail would help. As written, the payload is described only by example ('ツール実行・権限範囲など'), so an agent knows roughly what comes back but not exactly.

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 semantics to explain and the baseline is 4. The description raises no confusion about inputs.

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 a specific verb-and-resource pair (return the registered providers) and adds the payload scope: availability, tool execution, and permission scope. It is clearly distinguishable from list_models and list_agents by resource, though it never states that distinction explicitly.

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 when-to-use guidance and no named alternative. The mention of availability and permission scope only implies the use case (checking provider capabilities before running an agent); the agent must infer it.

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