Skip to main content
Glama

What one dialog cost

dosai_get_conversation_cost
Read-onlyIdempotent

Real charges for one dialog: cents = US cents taken from the project balance (bot replies, AI follow-ups, voice, image and video recognition, minus refunds), the number in the cabinet chat header; charges = rows behind it. cents null = nothing recorded (no bot reply, or older than 09.05.2026): do not estimate from tokens. Before 16.11.2026 replies to several messages at once are missing, so the sum may be lower.

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>",
      "conversation_id": "<conversation_id>"
    },
    "name": "dosai_get_conversation_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
conversation_idYesFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish readOnly, idempotent and non-destructive behavior, and the description goes well beyond them by explaining null semantics, the accounting formula behind cents (bot replies, follow-ups, voice, image/video recognition, minus refunds), and known data gaps in date ranges. It does not, however, describe the structure or volume of the 'charges' rows, which is the main behavioral unknown left.

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 definition is front-loaded with the meaning of cents, then charges, then the null case, then the data-gap caveat — a logical order with no filler. It is dense with parenthetical qualifiers and two hard dates, which makes it harder to scan than it needs to be, but every clause carries real information.

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 must explain the return values itself, and it does: cents is defined with its accounting basis and charges is identified as the underlying rows. The remaining gap is the shape and contents of those rows, which an agent cannot infer from the definition alone.

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 100% and both parameters are already documented with their source tools (dosai_list_projects, dosai_list_conversations). The description adds no extra meaning about project_id or conversation_id, so the baseline of 3 for a fully-documented schema 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?

The description opens with a specific verb-and-resource statement ('Real charges for one dialog') and immediately defines the two returned quantities (cents vs. charges), which is exactly what distinguishes this lookup from a token-based estimate or a balance lookup. An agent knows precisely what number it will get back.

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 gives a clear usage boundary — 'do not estimate from tokens' — and explains when the returned value will be null or understated (no bot reply, records older than 09.05.2026, multi-message replies before 16.11.2026). It never names a sibling tool as the alternative for aggregate or per-project cost, so the routing guidance is contextual rather than explicit.

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