Skip to main content
Glama

Run a new "what the bot is missing" check (paid)

dosai_start_bot_gaps_check

Start a new check that reads recent conversations and the bot's knowledge and finds questions without an answer. PAID from the project balance: tell the owner the price from dosai_list_bot_gaps (new_check_price: about typical_cents, never more than cap_cents) and get a yes first. Takes a few minutes; then read the result with dosai_list_bot_gaps. Not more often than once an hour. 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_start_bot_gaps_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
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.4/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint false, destructiveHint false, openWorldHint false) by disclosing the monetary charge against the project balance, the price fields and cap, the multi-minute runtime, the hourly throttle, and the admin/owner requirement — all facts an agent would otherwise miss.

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?

Front-loads the purpose, then immediately the cost warning, then timing, retrieval, throttle, and role. Every clause carries operational information; nothing is decorative.

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 an async, paid, rate-limited job with no output schema, the description supplies cost, duration, result retrieval, consent requirement, and permissions. The only remaining hole is the unexplained language parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about either parameter. project_id is documented in the schema, but the optional 'language' enum (ru/en/kz) is never explained — whether it controls the scan scope, the report language, or the bot's language is left entirely to inference at 50% schema coverage.

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 outcome: 'Start a new check that reads recent conversations and the bot's knowledge and finds questions without an answer.' It is clearly distinguishable from dosai_list_bot_gaps, which is named as the price/result reader rather than the starter.

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?

Explicit sequencing: fetch price via dosai_list_bot_gaps, get the owner's consent, then start, then read the result with the same sibling. It also gives an exclusion in the form of a rate limit ('not more often than once an hour') and a role prerequisite.

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