Skip to main content
Glama

What the bot finds for a question

dosai_search_knowledge

Search the knowledge base exactly as the bot does and show which pieces it would read for a client's question. Use it for "why did the bot not know the price". Costs a fraction of a cent. Requires editor role.

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

Input Schema

NameRequiredDescriptionDefault
questionYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: a monetary cost ('a fraction of a cent') and an authorization requirement ('editor role'), plus the important behavioral fact that results simulate bot retrieval rather than a raw index lookup. This also reconciles the readOnlyHint=false annotation, since billing is a side effect of a semantically read-like call.

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 sentences with zero padding: what it does first, then the use case, then cost and permission. Every sentence carries information an agent would otherwise have to guess.

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?

For a two-parameter, non-destructive tool with no output schema, the definition covers purpose, trigger, cost, and access requirements, and it sketches the shape of the return ('which pieces it would read'). Only the question-parameter phrasing conventions are left unstated.

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 only 50%: project_id is documented ('From dosai_list_projects') but the question parameter carries no description. The phrase 'for a client's question' hints that it should be phrased as the end user would ask it, but that inference is left implicit rather than stated.

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 ('Search the knowledge base') plus a precise scope: it replays retrieval exactly as the bot does and reports which pieces it would read. This is distinguishable from a plain knowledge listing or a conversation search 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 a concrete triggering scenario ('why did the bot not know the price') and a prerequisite ('Requires editor role'), which is more than most definitions offer. It stops short of naming when to prefer a sibling such as dosai_list_knowledge or dosai_search_conversation, so no explicit exclusion is stated.

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