Skip to main content
Glama

One function of the bot (read only)

dosai_get_function
Read-onlyIdempotent

Read-only details of one function of the DOS AI bot, a saved setting the bot follows in its own chats with clients: when the bot uses it, its parameters and whether it is on. Not an operation of this server: reading executes nothing. Secrets are masked by the server. 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>"
    },
    "name": "dosai_get_function"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: reading executes nothing because this is a saved config rather than a server operation, secrets are masked by the server, and editor role is required. Those three facts materially change how an agent interprets the result and whether it can call the tool.

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?

A single front-loaded sentence leads with the read-only scope, then a colon list of returned information, then two short clarifiers. Dense but every clause carries information; the colon-plus-list construction is slightly crowded but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two well-documented required params and no output schema, the description supplies what the schema cannot: what a returned record contains (usage timing, parameters, active state), that secrets are masked, and the role required. Nothing an agent needs to call this correctly is missing.

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 carry their own provenance notes ('From dosai_list_projects', 'From dosai_list_functions'), so the schema does the heavy lifting. The description adds no input-parameter detail; its clause about 'when the bot uses it, its parameters and whether it is on' describes returned fields, not inputs. Baseline 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 gives a specific verb and resource ('Read-only details of one function of the DOS AI bot') and goes further by defining what a 'function' is here (a saved setting the bot follows in its own chats), which is non-obvious terminology. It does not name a sibling to contrast with (e.g. dosai_list_functions or dosai_get_bot_settings), 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you read one function's details, and the prerequisite 'Requires editor role' is disclosed. There is no explicit when-to-use / when-not guidance or named alternative for bulk listing versus single retrieval; that routing only appears indirectly in the schema's 'From dosai_list_functions' notes.

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