Skip to main content
Glama

Choose the bot's AI model

dosai_set_model
Destructive

Change the AI model the bot answers with. A smarter model costs more per answer, so confirm with the owner. Models: gpt-5.5: Предельно сложные задачи (дорого): экспертный анализ, тонкий reasoning; gpt-5.4-mini: Универсальный выбор: продажи, поддержка, консультации; gpt-5.4: Сложные задачи: юриспруденция, медицина, аналитика; gpt-5.4-nano: Самый экономичный вариант: простые боты, FAQ, запись; gpt-5-mini: Экономичный универсал: продажи, поддержка, консультации; gpt-5: Сложные задачи, длинные контексты; gpt-5.1: Боты с детальными инструкциями, стабильная работа; gpt-5.2: Сложная аналитика, экспертные консультации; gpt-4.1-mini: Бюджетный старт: продажи, запись, консультации; gpt-4.1: Стабильные боты с чёткими инструкциями. Requires admin or owner 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>",
      "model": "<model>"
    },
    "name": "dosai_set_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
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. Changed1 schema field changed
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "gpt-5.5",
      -  "gpt-5.4-mini",
      -  "gpt-5.4",
      -  "gpt-5.4-nano",
      -  "gpt-5-mini",
      -  "gpt-5",
      -  "gpt-5.1",
      -  "gpt-5.2",
      -  "gpt-4.1-mini",
      -  "gpt-4.1",
      -  "gpt-4.1-nano"
      -]New value: +[
      +  "gpt-5.5",
      +  "gpt-5.4-mini",
      +  "gpt-5.4",
      +  "gpt-5.4-nano",
      +  "gpt-5-mini",
      +  "gpt-5",
      +  "gpt-5.1",
      +  "gpt-5.2",
      +  "gpt-4.1-mini",
      +  "gpt-4.1"
      +]
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral context: the cost tradeoff per answer and the admin/owner authorization requirement. It stops short of saying whether the change applies immediately or only to new conversations, which is the remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the cost warning are front-loaded, which is good structure, and the model list is functional rather than filler. But the list is long and switches mid-sentence into Russian while the rest of the description is English, hurting scannability and consistency for an agent parsing it.

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 two-parameter mutation with no output schema, the description covers purpose, cost implications, authorization, and per-model selection guidance. The only meaningful omission is the effect on in-flight conversations and whether the switch is immediate.

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 50%, with project_id documented in the schema ('From dosai_list_projects'). The description compensates for the undocumented enum by annotating all ten model values with use-case and cost guidance, which is meaning the bare enum cannot convey. It adds no detail on project_id, but the schema already covers that.

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: 'Change the AI model the bot answers with.' This is clearly distinct from sibling settings tools like dosai_update_bot_settings or dosai_get_bot_settings, and the scope (one bot's answering model) is unambiguous.

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 gives a real precondition ('Requires admin or owner role') and a caution ('A smarter model costs more per answer, so confirm with the owner'), which is useful when-to-use context. However, it never names an alternative or explains when to prefer this over the broader dosai_update_bot_settings, so routing guidance is only implied.

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