Skip to main content
Glama

What price the bot would calculate

dosai_check_price_quote

Calculate a price exactly as the bot would, free and without the AI: write the phrase as a client would ("2 windows, 266 and 298 cm", "salmon fillet 1.5 kg"). For a price by sizes also pass the item's key. Use it to show the owner the price list works. Changes nothing, but needs access with the right to write.

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>",
      "list_id": "<list_id>",
      "text": "<text>"
    },
    "name": "dosai_check_price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
list_idYesPrice list id from dosai_get_price_list.
item_keyNoThe item's key, for a price by sizes.
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 / list_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 / 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.5/5.0
Behavior5/5

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

The description reconciles the readOnlyHint=false annotation by explaining that the call 'Changes nothing, but needs access with the right to write' – the non-obvious fact that a compute-only preview still requires write-scoped credentials. It also discloses the 'free, without the AI' cost behavior, which nothing in the schema or annotations conveys.

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?

Front-loaded with the purpose, then input guidance, then the permissions caveat – a logical order with no filler. The inline examples are dense but earn their place by showing the expected phrasing format.

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?

There is no output schema, so the description carries the burden of describing results, and it only implies a price comes back – it says nothing about the response shape or what happens when the phrase cannot be matched to an item. For a preview tool with four parameters, that is the main remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds genuinely useful semantics for the free-text parameter by giving client-style examples ('2 windows, 266 and 298 cm', 'salmon fillet 1.5 kg') and by explaining that item_key is only needed 'for a price by sizes'. project_id and list_id remain schema-only, which is acceptable given their descriptions.

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 ('Calculate a price exactly as the bot would') and immediately scopes it as a dry-run preview ('free and without the AI'). An agent can distinguish this from dosai_get_price_list or dosai_get_reply_price: this one evaluates free text, not stored data.

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?

'Use it to show the owner the price list works' gives a concrete scenario for invocation, and 'write the phrase as a client would' constrains input preparation. No explicit when-not conditions or named fallback tool are given, so it stops short of a 5.

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