Skip to main content
Glama

Auto-reply to a word

dosai_add_keyword_reply

Create a rule: when a client writes one of the words, the platform instantly sends this exact text without the AI (e.g. the word "price" gets the price list). Only real text, never placeholders like [address]: it goes to real clients as written. 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": "<name>",
      "keywords": "<keywords>",
      "reply": "<reply>"
    },
    "name": "dosai_add_keyword_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort rule name the owner will recognise.
matchNoword (default) = the whole word anywhere, contains = inside any word, starts = message starts with it, exact = the whole message.
replyYesExactly what the client receives.
keywordsYes
frequencyNoonce_per_conversation (default), once_per_contact, or every time.
project_idYesFrom dosai_list_projects.
first_message_onlyNoOnly in the client's first message (ads with pre-filled text).

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

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds real operational context: the text is sent instantly and verbatim to real clients, so placeholders like [address] would leak, and an editor role is required. It does not cover rule conflicts, edit/delete of existing rules, or limits, but the added behavioral warnings are genuinely useful.

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?

A single dense sentence pair that front-loads the trigger and effect, then the real-client warning and role requirement. Every clause carries information; the parenthetical example is justified because it clarifies the mechanism.

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 7-parameter creation tool with no output schema, the description covers trigger, effect, fidelity warning, and permission requirement, which is enough to call it correctly. Minor gaps remain around what the tool returns (rule id?) and how it interacts with existing rules.

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 description coverage is 86%, with enums already documented for match and frequency and a pointer to dosai_list_projects for project_id. The description only reinforces 'one of the words' and 'this exact text', adding little meaning beyond the schema, so the baseline 3 applies.

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 ('Create a rule') plus the exact trigger and effect: when a client writes one of the words, the platform sends the given text without the AI. The 'price' example and the 'without the AI' clause make it distinguishable from AI-driven reply tools in the sibling set.

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 clear usage context (deterministic keyword-triggered replies, e.g. price list) and states the prerequisite 'Requires editor role.' It does not explicitly name an alternative tool or state when NOT to use this versus an AI/knowledge-based reply, so it falls short of full routing guidance.

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