Skip to main content
Glama
Sign In
Tiny Chat

Tiny Chat

by to-aoki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search-default

Retrieve relevant information from vector-based knowledge bases using semantic search. Query Qdrant collections with configurable top-k and score threshold for retrieval-augmented generation.

Instructions

default Information Collection Store

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search-default"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
top_kNo
score_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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.

Deploy Server

Other Tools