Skip to main content
Glama

list_platforms

Identify all platforms supported for skill sharing, helping AI agents select compatible environments.

Instructions

List all supported platforms (ClaudeCode, Cursor, CodexCLI, GeminiCLI, OpenClaw, CustomAgent, etc.). / 지원 플랫폼 목록.

Returns: 플랫폼 목록 문자열

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'list_platforms' tool handler function. Decorated with @mcp.tool() and @_log_tool. Calls _get('/v1/platforms') and formats the response listing supported platforms.
    @mcp.tool()
    @_log_tool
    def list_platforms() -> str:
        """
        List all supported platforms (ClaudeCode, Cursor, CodexCLI, GeminiCLI, OpenClaw, CustomAgent, etc.). / 지원 플랫폼 목록.
    
        Returns:
            플랫폼 목록 문자열
        """
        result = _get("/v1/platforms")
        if result.get("status") == "error":
            return f"오류: {result.get('message')}"
        platforms = result.get("platforms", [])
        if not platforms:
            return "등록된 플랫폼이 없습니다."
        lines = ["지원 플랫폼:"]
        for p in platforms:
            lines.append(f"• {p.get('name')} — {p.get('description', '')}")
        return "\n".join(lines)
  • Tool registration via @mcp.tool() decorator on the list_platforms function.
    @mcp.tool()
  • The _get helper function used by list_platforms to make HTTP GET requests to the skill store API.
    def _get(path: str, params: dict = None) -> dict:
        url = SKILL_STORE_URL + path
        if params:
            url += "?" + urllib.parse.urlencode({k: v for k, v in params.items() if v is not None})
        try:
            with urllib.request.urlopen(url, timeout=10) as resp:
                return json.loads(resp.read().decode())
        except urllib.error.HTTPError as e:
            return {"status": "error", "message": f"HTTP {e.code}: {e.reason}"}
        except Exception as e:
            return {"status": "error", "message": str(e)}
Behavior3/5

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

No annotations are provided, placing the burden on the description. The description indicates a read-only list operation, but does not disclose any behavioral traits such as data source, caching, or side effects. Adequate for a simple list 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?

The description is very concise with two sentences (English and Korean), front-loading the purpose. The inclusion of a return type adds value, though it is slightly redundant given the output schema.

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?

Given no parameters and an existing output schema, the description is reasonably complete. It specifies the resource and return type, leaving little ambiguity for a simple list tool.

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 tool has zero parameters, so schema coverage is trivially 100%. The description adds no parameter meaning beyond the schema, aligning with the baseline of 3 for high coverage.

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' and the resource 'supported platforms', with examples of platform names. It is specific and distinguishes itself from sibling tools, none of which list platforms.

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?

No explicit guidance on when to use this tool versus alternatives, nor when not to use it. The simplicity of the tool partially excuses this, but the dimension requires explicit context.

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/garasegae/aiskillstore'

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