Skip to main content
Glama

Ask Tridan AI

ask_assistant

Send a message to "Tridan AI", the AI assistant behind "Tridan-AI SRB", and get its full answer (it has its own instructions, knowledge base and tools). Returns a conversation_id — pass it back to continue the same conversation.

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": {
      "question": "<question>"
    },
    "name": "ask_assistant"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe message to send to the assistant
conversation_idNoContinue an earlier conversation: pass the conversation_id a previous ask_assistant call returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds the important behavioral fact that the target is an autonomous assistant with its own instructions, knowledge base and tools, meaning replies are non-deterministic and beyond this server's control. It also discloses the returned conversation_id and how it is reused, which is not derivable from the annotations. It stops short of latency, cost, or side-effect disclosure, which keeps it below 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.

Conciseness4/5

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

Two compact sentences with no wasted clauses, front-loading the action and following with the return/continuation detail. The nested quoting of product names ('Tridan AI', 'Tridan-AI SRB') is slightly noisy but does not impede parsing.

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?

With no output schema, the description correctly covers the return surface: the full answer plus a conversation_id for chaining. For a two-parameter tool with full schema coverage, the only meaningful omission is that it does not say the underlying assistant may perform its own tool calls or take time, which matters for an agent deciding whether to call it.

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% and both fields are already documented with a length cap and UUID pattern, so the schema carries the burden. The description only restates the conversation_id continuation semantics already present in the schema; it adds no extra constraints or format detail. Baseline 3 applies.

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

Purpose4/5

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

States a concrete verb+resource: send a message to the 'Tridan AI' assistant and get its full answer, plus the identity of the backing system (Tridan-AI SRB). It hints at differentiation by noting the assistant has its own instructions, knowledge base and tools, but it never explicitly contrasts itself with the sibling query_knowledge_base, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

The continuation rule is spelled out ('pass conversation_id back to continue the same conversation'), which is real usage guidance. However, there is no when-to-use vs. when-not guidance relative to query_knowledge_base, and no statement about what kinds of questions belong here versus a direct knowledge-base lookup.

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