Skip to main content
Glama
ilhankilic

YaparAI MCP Server

by ilhankilic

list_chatbots

Retrieve all active chatbots on YaparAI, including their slug, name, description, and configuration. Use the slug to initiate a chat with a specific bot.

Instructions

List all available chatbots on YaparAI.

Returns active chatbots with their slug, name, description, and configuration. Use the slug to chat with a specific bot. No credits charged.

Returns: List of chatbot configs with slug, name, description, avatar_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler that creates a client instance and calls the client's list_chatbots method.
    async def list_chatbots() -> dict:
        """
        List all available chatbots on YaparAI.
    
        Returns active chatbots with their slug, name, description,
        and configuration. Use the slug to chat with a specific bot.
        No credits charged.
    
        Returns:
            List of chatbot configs with slug, name, description, avatar_url.
        """
        client = YaparAIClient()
        return await client.list_chatbots()
  • HTTP client method that sends a GET request to /v1/chatbot/list to fetch active chatbots.
    async def list_chatbots(self) -> list:
        """List active chatbots."""
        return await self._request("GET", "/v1/chatbot/list")
  • Registration of list_chatbots as an MCP tool on the FastMCP server.
    mcp.tool(list_chatbots)
  • Import of list_chatbots from the chatbot tools module into the server.
    # --- Chatbot ---
    from yaparai.tools.chatbot import (
        list_chatbots,
        chat_with_bot,
    )
Behavior3/5

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

With no annotations, the description carries full burden. It mentions a positive behavioral trait (no credits charged) and reports active chatbots, but lacks details on authentication, rate limits, or pagination. Adequate for a simple list.

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?

Three sentences with no fluff. The first sentence states the purpose, the second details the return structure, and the third provides a usage note. Very 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?

Given zero parameters and an output schema, the description covers the essential: what the tool does, what it returns, how to use the result (slug), and that it is free. No major gaps.

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?

Input schema has zero parameters, so baseline is 4. Description adds value by listing the return fields (slug, name, description, avatar_url), which helps the agent understand the output even though an output schema exists.

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?

Description clearly states the tool lists all available chatbots on YaparAI, and specifies the returned fields (slug, name, description, configuration). It also differentiates from the sibling tool 'chat_with_bot' by noting to use the slug for chatting.

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?

Description provides a usage hint ('Use the slug to chat with a specific bot') and notes 'No credits charged', but does not explicitly state when not to use or list alternatives. The usage is implied by the tool's purpose.

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/ilhankilic/yaparai-mcp'

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