Skip to main content
Glama
Datris MCP Server

Datris MCP Server

search_weaviate

Run semantic search against a Weaviate vector class: converts a natural language query into an embedding and returns the most similar document chunks with similarity scores for RAG.

Instructions

Semantic search across a Weaviate vector database class. Takes a natural language query, generates an embedding, and returns the most similar document chunks with similarity scores. For RAG: pass the returned text to ai_answer with the user's question.

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_weaviate"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language search query
top_kNoNumber of results to return (default: 5)
class_nameNoWeaviate class name (default: Documents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the operational mechanics: the query is embedded and results come back ranked with similarity scores, which sets expectations for latency and cost of an embedding call. It omits failure behavior (unknown class_name, empty index) and any result-cap behavior, keeping it short of a 5.

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 tight sentences with the core action front-loaded, followed by return-value detail and then the RAG handoff instruction. Every sentence carries distinct information with no repetition.

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?

No output schema exists, so the description usefully compensates by describing the return as document chunks with similarity scores, and the ai_answer pointer closes the loop on consumption. For a three-parameter read tool this is nearly complete; only error and result-size behavior are unaddressed.

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?

Schema description coverage is 100%, so query, top_k, and class_name are already documented with defaults in the schema. The description reinforces the natural-language nature of the query but adds no constraints, formats, or semantics beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ('Semantic search across a Weaviate vector database class') and spells out the mechanism (embedding generation, similarity-ranked chunks). Naming Weaviate, plus the pointer to ai_answer, makes it easy to tell apart from the sibling vector-store searches without opening any schema.

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?

Gives concrete downstream guidance: 'For RAG: pass the returned text to ai_answer with the user's question,' which establishes the intended workflow and the relationship to the ai_answer sibling. It does not state when to prefer this over the other vector-store search tools, but no exclusions are implied and the guidance present is actionable.

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