Skip to main content
Glama

Switch a function on or off

dosai_set_function_active
Destructive

Turn a bot function on or off, e.g. stop the bot from booking while the calendar is being fixed. 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>",
      "function_id": "<function_id>",
      "is_active": "<is_active>"
    },
    "name": "dosai_set_function_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_activeYes
project_idYesFrom dosai_list_projects.
function_idYesFrom dosai_list_functions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / function_id / description
      Previous value: -"Function id, as returned by dosai_list_functions."New value: +"From dosai_list_functions."
  2. 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."
  3. Changed2 schema fields changed
    • removedInput schema / properties / function_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)$"
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Adds real value beyond annotations by disclosing the editor-role authorization requirement, which annotations do not carry. However, it does not say what the toggle actually affects (in-flight conversations, scheduled runs), whether it is idempotent when the function is already in the requested state, or whether the change is reversible beyond toggling back. The destructiveHint=true annotation covers the risk profile, so this gap is limited but real.

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

Conciseness5/5

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

Two sentences, front-loaded with the action, then a concrete example, then the permission constraint. Every clause earns its place with no filler.

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 three-parameter binary toggle with no output schema, the description covers purpose, a motivating example, and the authorization requirement. The remaining unspecified item is the functional effect of deactivation on running work, which is minor for a simple on/off switch.

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 coverage is 67% and the two UUID parameters already carry sourcing hints ('From dosai_list_projects', 'From dosai_list_functions'); the description adds no meaning to any parameter. The boolean is_active is self-explanatory, so the baseline of 3 for adequate schema coverage 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?

States a specific verb and resource: 'Turn a bot function on or off', with the exact object of the toggle named. It does not distinguish itself from the related sibling dosai_set_rule_active, which shares the same activate/deactivate shape, so it stops short of a 5.

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?

Gives a concrete triggering scenario ('stop the bot from booking while the calendar is being fixed') and a prerequisite ('Requires editor role'), so an agent knows the situation this is for. It stops short of explicit exclusions or naming an alternative tool for the rule-level equivalent.

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