Skip to main content
Glama

The owner's own auto-reply that gets in the bot's way

dosai_get_own_autoreply_warning
Read-onlyIdempotent

Whether the platform noticed an auto-reply set up in the owner's own messenger app (WhatsApp Business greeting, Instagram instant reply): its text, channel, when it was seen and in how many new chats. Such an auto-reply answers before the bot and the bot may stay silent in that chat, so the owner should switch it off in the app itself. null = nothing noticed. 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>"
    },
    "name": "dosai_get_own_autoreply_warning"
  }
}

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.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, yet the description still adds real value: the null-means-nothing-noticed contract, the 'Requires editor role' authorization requirement, and the consequence that the bot may stay silent in that chat. What it does not cover is the response envelope or whether the warning is per-project or per-channel scope, which keeps it from 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?

Purpose is front-loaded, followed by the operational consequence and then the null contract, with no filler sentences. The opening sentence is long and packs the return fields, the diagnosis, and the remediation into one clause chain, which slightly reduces scannability.

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 carries the burden of describing the return value, and it does so concretely (text, channel, observation time, count of new chats) plus the null case. The only gap is the absence of any note on how the warning is dismissed, which matters given the sibling dismiss tool exists in the same family.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself noting 'From dosai_list_projects.', so the baseline of 3 applies. The description contributes nothing further about project_id (e.g., that the warning is scoped to that project's owner).

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?

The description names a specific retrieved resource: whether the platform noticed an auto-reply in the owner's own messenger app, and enumerates the fields returned (text, channel, when seen, chat count). This is clearly a read of a warning/status object, distinguishable from the sibling dosai_dismiss_own_autoreply_warning, which acts on the same object.

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 rather than stated: the reader infers this is called to check whether a host-app auto-reply is intercepting chats, and the description directs remediation ('the owner should switch it off in the app itself'), which usefully steers the agent away from bot-side fixes. There is no explicit when-to-call, no condition such as 'call before configuring bot behavior', and no named alternative for clearing the warning.

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