Skip to main content
Glama

Search Tridan-AI SRB knowledge base

query_knowledge_base
Read-only

Semantic search over the knowledge base behind "Tridan-AI SRB" (assistant: Tridan AI). Returns the most relevant text chunks with their source URLs — no answer is generated, synthesize one yourself from the chunks. Use ask_assistant when you want the assistant to 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>"
    },
    "name": "query_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language question to search the knowledge base with
top_kNoHow many chunks to return (default: the widget's own setting, max 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so safety is covered. The description adds the important non-obvious trait that raw chunks with source URLs are returned rather than a synthesized answer, which changes how an agent must post-process results.

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 short clauses, front-loaded with the core capability, followed by return shape and then the routing alternative. No redundant or filler wording.

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?

No output schema exists, and the description compensates by describing the return value (most relevant text chunks with source URLs). Combined with the sibling routing and full schema, an agent has everything needed to call and interpret it correctly.

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 coverage is 100% and both parameters (query, top_k) are fully documented in the schema, including bounds and default. The description adds no syntax or format meaning beyond that, so the baseline of 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 mechanism (semantic search) over a named resource (the knowledge base behind "Tridan-AI SRB") and immediately differentiates itself from the sibling by noting no answer is generated.

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

Usage Guidelines5/5

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

Explicitly names the alternative (ask_assistant) and the condition that selects it ('when you want the assistant to answer'), plus the positive case: synthesize an answer yourself from the returned chunks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources