Skip to main content
Glama
to-aoki

Tiny Chat

by to-aoki
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Tiny Chat

Ask DeepWiki

Installation

Tested with Python 3.10 or later

Development Installation

pip install -r requirements.txt

Package Installation

# Build the package
pip install build
python -m build

# Install the built package
pip install dist/*.whl

Related MCP server: RAG MCP Server

Web Interface Usage

Running from source (development)

streamlit run tiny_chat/main.py --server.address=127.0.0.1

only database (development)

streamlit run tiny_chat/main.py --server.address=127.0.0.1 -- --database

Running installed package

tiny-chat

only database

tiny-chat --database

img.png

MCP Usage

Claude Desktop example.

{
  "mcpServers": {
    "tiny-chat": {
      "command": "/path/to/tiny_chat/.venv/bin/tiny-chat-mcp",
      "env": {
        "DB_CONFIG": "/path/to/tiny_chat/database_config.json"
      }
    }
  }
}

OpenAI Chat API RAG Server Usage

tiny-chat-api

model: target search qdrant collection name (model change in conversation).

curl http://localhost:8080/v1/chat/completions   -H "Content-Type: application/json"   -d '{"model": "qdrant-collection-name", "messages": [{"role": "user", "content": "カレーライスの材料は？"}]}'

Available Tools

1 tool
search-defaultD

default Information Collection Store

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo
score_thresholdNo

TDQS

D1/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It reveals nothing about side effects, permissions, return behavior, or limitations. It is essentially empty of behavioral information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is short, it is an under-specified placeholder, not an appropriately sized description. It lacks any useful content and does not earn its place.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 parameters, no output schema, and no annotations, the description is completely inadequate. It provides no context for how the tool should be used or what it returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to the parameters. The parameter names (query, top_k, score_threshold) suggest functionality, but the description fails to explain them or their semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'default Information Collection Store' does not state what the tool does. It is a vague placeholder that does not specify a verb, resource, or action, and provides no differentiation from any other tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool or when not to. The description gives no context, prerequisites, or alternative comparisons.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedsearch-default
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.5/5.0
Disambiguation5/5

With only one tool, there is no possibility of selecting between overlapping tools. The vague description does not create disambiguation issues.

Naming Consistency3/5

With a single tool, there is no pattern to evaluate for consistency. The name 'search-default' is unconventional but does not conflict with other naming styles.

Tool Count1/5

A single tool for a chat-focused server is clearly insufficient. The tool 'search-default' appears trivial and not aligned with the server's apparent domain.

Completeness1/5

The server provides no chat-related operations such as messaging or channel management. It appears severely incomplete for a chat server, offering only a vague search capability.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • mcp-rag-server

    kwanLeeFrmVi
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that indexes documents and serves relevant context to LLMs via Retrieval Augmented Generation (RAG).
    48
    37
    MIT

  • RAG MCP Server

    tungetti
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server for Retrieval-Augmented Generation (RAG) operations. It provides tools for building and querying vector-based knowledge bases from document collections, enabling semantic search and document retrieval capabilities.
    3
    MIT

  • THE RAG MCP

    Sankalp-2005
    F
    license
    Not graded
    quality
    D
    maintenance
    An enterprise-ready MCP server that exposes a RAG tool for retrieving relevant context and metadata from a Qdrant vector database using natural language queries.
    2
    -

  • rag-mcp

    Ma-fee
    F
    license
    Not graded
    quality
    D
    maintenance
    A RAG service based on FastMCP that enables document indexing and retrieval (keyword/vector search) through the MCP protocol.
    -

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/to-aoki/tiny_chat'

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