Skip to main content
Glama

Check that a report can be delivered

dosai_check_report_delivery

A live check for one report (ids: dosai_list_report_settings): does the bot that sends it see the target Telegram chat and may it write there, is the email set. Sends NOTHING and changes nothing. Answers "why did yesterday's report not arrive": every check comes with ok and what is wrong. Owner only.

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>",
      "report_id": "<report_id>"
    },
    "name": "dosai_check_report_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYes
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. Changed2 schema fields 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)$"
    • removedInput schema / properties / report_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
Behavior2/5

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

The description adds real behavioral context beyond the annotations: per-check 'ok' plus a reason, no delivery attempted, owner-only authorization. However, 'Sends NOTHING and changes nothing' asserts read-only semantics while the annotations declare readOnlyHint: false, an inconsistency that could make an agent wrongly assume the call is side-effect free or, conversely, distrust the annotation.

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?

Dense but front-loaded: the core action comes first, then the no-side-effect constraint, then the diagnostic payoff and permission requirement. The parenthetical id-source note is slightly awkward but earns its place by linking to the sibling tool.

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 explains the return shape (each check reports ok plus what is wrong). It covers the safety profile of not delivering anything and the owner-only restriction. The only gap is the unresolved tension with readOnlyHint and the thin explanation of the two ids.

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 50%: project_id carries a 'From dosai_list_projects' note, report_id has none. The description partially compensates by pointing at dosai_list_report_settings as the id source, but it doesn't disambiguate which id comes from which tool or clarify the scope of 'one report' versus a project.

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 ('a live check for one report') and enumerates exactly what is verified: bot visibility of the target Telegram chat, write permission there, and whether the email is set. It names the sibling that supplies the ids (dosai_list_report_settings), so an agent can distinguish it from the sibling check tools without opening a 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 trigger scenario ('why did yesterday's report not arrive') and implicitly separates itself from the sending path by stressing 'Sends NOTHING and changes nothing'. It also states an access prerequisite ('Owner only'). It stops short of explicitly naming the alternative to use when the goal is to actually deliver (e.g. dosai_send_report_now) or of stating when not to run this check.

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