Skip to main content
Glama

The price list the bot calculates by

dosai_get_price_list
Read-onlyIdempotent

The project's price list: the working one and an uploaded draft, where each came from (a file or a Google Sheet), whether the bot calculates by it, the items with their ids (needs_confirm=true: the owner must confirm the grid was read correctly before the list can be switched on), problems found while reading the file, and earlier versions. A file is uploaded by the owner in the cabinet; a Google Sheet is connected with dosai_connect_price_sheet.

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_price_list"
  }
}

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real domain behavior beyond that: the needs_confirm flag means the owner must confirm the grid was read correctly before the list can be switched on, and it surfaces read-time problems and version history. It is missing any note on size limits or ordering of earlier versions.

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?

It is front-loaded with the resource and free of filler, but it is one long comma-chained sentence with several nested parentheticals, which makes it slower to parse than a short enumerated list would be. Every clause does carry information, so little is wasted.

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 does so thoroughly: sources, per-item ids, the confirm flag, read errors, and prior versions. For a one-parameter read on a single project this is close to complete, with only limits on history depth or list size left unspecified.

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?

There is a single parameter and schema coverage is 100%, with the schema itself pointing to dosai_list_projects for the project_id value. The description contributes no additional meaning about the identifier or how it scopes the returned list, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource and enumerates its parts (working list vs. uploaded draft, source, calculation flag, items with ids, read problems, earlier versions), so an agent knows exactly what it is fetching. It falls short of a 5 because it is written as a noun phrase describing returned content rather than stating the retrieval verb explicitly, though the read is unambiguous in context.

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?

It clarifies the provenance paths (owner uploads a file in the cabinet, Google Sheets go through dosai_connect_price_sheet), which implies this tool is for inspecting the list rather than creating or connecting it. However, it never says when to call this versus dosai_manage_price_list or dosai_get_reply_price, and gives no prerequisites or exclusions.

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