Skip to main content
Glama

Questions the bot cannot answer yet

dosai_list_bot_gaps
Read-onlyIdempotent

"What the bot is missing": clients' questions the bot has no answer to, found by the platform's paid check (from real conversations and from what is typical for the business). For each: the question, why it matters, how often clients asked, the owner's answer if given, status (open = waiting for the owner, draft = answered, human = "let a person answer", applied = written into the bot). Also the price of a new check, the balance, and whether a check is running. Requires admin or owner 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>"
    },
    "name": "dosai_list_bot_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description still adds real context: the data originates from a paid check over real conversations plus business-typical questions, the status vocabulary is decoded (open/draft/human/applied), and the admin-or-owner auth requirement is disclosed. It omits whether the response is paginated or what happens when no check has ever run.

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?

Purpose is front-loaded in the opening clause and every subsequent sentence adds substantive detail about returned fields, statuses, and access requirements. It is a single dense paragraph and the enumeration runs on, but nothing is genuinely redundant.

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 takes on the return-value burden and describes the per-item fields, the status meanings, and the accompanying price/balance/check-running information. That covers what an agent needs to interpret results, with pagination and empty-state behavior being the only notable gaps.

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?

There is a single parameter with 100% schema description coverage ('From dosai_list_projects.'), so the schema carries the semantics and the baseline of 3 applies. The description adds no further meaning about project_id or its sourcing beyond what the schema already says.

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?

The description gives a concrete resource definition — clients' questions the bot cannot answer, sourced from the platform's paid check — and enumerates the fields returned, which is far more specific than the bare name. It stops short of naming the adjacent siblings (dosai_start_bot_gaps_check, dosai_answer_bot_gap, dosai_write_bot_gaps), so an agent must infer the boundary from names alone.

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?

Usage is implied by the content ('questions the bot has no answer to') and a hard prerequisite is stated ('Requires admin or owner role'), which helps gate the call. However there is no explicit when-to-use versus when-not framing and no pointer to the sibling tools that start a check or answer a gap, so routing between them is left to inference.

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