Skip to main content
Glama
Datris MCP Server

Datris MCP Server

ai_answer

Answers user questions by synthesizing provided context for retrieval-augmented workflows that pass retrieved text with the query.

Instructions

Ask the Datris AI to answer a question based on provided context. Ideal for RAG workflows: first retrieve relevant chunks using a search tool (search_qdrant, search_pgvector, etc.), then pass the retrieved text as context along with the user's question to get a synthesized answer.

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>",
      "context": "<context>"
    },
    "name": "ai_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question to answer
contextYesContext text to base the answer on (e.g., retrieved document chunks)
sourcesNoOptional provenance handles for the context (e.g. find_data results or _datris_* fields from search hits). Echoed back unchanged on the response so the answer and its provenance travel together.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the core behavior — answer synthesis grounded in caller-supplied context, and that sources are echoed back unchanged so provenance travels with the answer — but says nothing about the response shape, latency/cost of an LLM call, or what happens when context is irrelevant or oversized.

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?

Two tight sentences with the action front-loaded and the workflow guidance second; nothing is wasted. Slightly compact on the return side, which is the only thing keeping it from being fully optimised.

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

Completeness3/5

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

With no output schema, the description should say roughly what comes back (an answer string plus the echoed sources) and any input limits. It hints at provenance echo but leaves the response contract implicit, which is a notable gap for a three-parameter synthesis tool with no annotations.

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 the schema already documents all three parameters; the baseline is 3. The description reinforces that context should be retrieved text and that sources are echoed back, but adds no format or size constraints beyond what the schema and its field descriptions already state.

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?

"Ask the Datris AI to answer a question based on provided context" states a specific verb (ask/answer) and resource (a synthesized answer), and immediately frames the tool's role relative to the search siblings. An agent can distinguish this from search_qdrant/search_pgvector without opening a 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?

Explicitly prescribes the workflow: retrieve chunks with a search tool first, then pass the retrieved text as context. It names concrete alternatives (search_qdrant, search_pgvector) and the ordering, but gives no exclusion — e.g. when to skip RAG and answer directly, or what to do when search returns nothing.

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