Skip to main content
Glama

What one bot reply costs

dosai_get_reply_price
Read-onlyIdempotent

What a bot reply costs this project, from real charges: replies is how many client messages the bot answered in WhatsApp, Telegram and Instagram over the last 30 days (test chat is not counted; a reply that failed to send and was refunded still counts), cents is how many US cents were taken from the project balance for them, knowledge_entries is the number of records in the knowledge base. When there are at least 20 replies, price holds cents_per_reply (the average; the cabinet shows the owner the same number rounded to whole cents) and replies_per_10_usd. price is null with fewer replies or when nothing was charged: there is not enough history, do not divide the two numbers yourself. A long prompt and a big knowledge base make every reply dearer. 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_reply_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses exactly what counts as a reply, that test chat is excluded, that refunded failed sends still count, that editor role is required, and why price may be null. That is substantial behavioral context for a read-only reporting tool.

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?

The description is front-loaded with what the tool measures and every sentence carries relevant calculation, caveat, or return-value information. It remains a dense single paragraph rather than a clearly structured breakdown, which slightly hurts readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description carries the burden of explaining replies, cents, knowledge_entries, and the nullable price object. It does this thoroughly, including threshold, rounding, and ratio behavior, so an agent can interpret the result correctly.

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?

The only parameter, project_id, is fully described in the schema as coming from dosai_list_projects. The description adds no further parameter guidance, so the schema baseline of 3 is appropriate.

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 states a precise verb and resource: it reports what one bot reply costs this project, computed from real charges over the last 30 days. It is specific enough to distinguish this from balance and price-list siblings without needing to name them.

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?

It clearly defines the context in which the result is meaningful: at least 20 replies and actual charges, otherwise price is null. It does not explicitly route the agent away from alternatives such as dosai_get_balance or dosai_get_price_list, so it lacks full when-not 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