Skip to main content
Glama

List the bot's functions (read only)

dosai_list_functions
Read-onlyIdempotent

Read-only list of the DOS AI bot's functions: saved settings (called «Функции» in the cabinet) that the bot follows by itself in its own chats with clients, e.g. book into Google Calendar, notify the owner, write a Google Sheet, call the owner's webhook. They are data, not operations of this server: no tool here executes a function, and reading the list executes nothing. Secret values are masked by the server.

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

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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond them: it clarifies that reading the list executes nothing and that secret values are masked by the server — a disclosure an agent could not get from annotations alone. Return shape (ordering, pagination, per-item fields) is not described.

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 operation and scope, followed by the definition, the data-vs-operations clarification, and the masking note. Each sentence carries information, though the illustrative list of function types and the "in its own chats with clients" clause make it slightly longer than strictly necessary.

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 and a single fully-documented parameter, the description covers what is needed: what is returned conceptually (the bot's saved functions), that values are masked, and that nothing is executed. Missing only minor return details such as ordering or item structure, which are low-risk for a simple read-only list.

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?

The single project_id parameter is fully documented in the schema (format uuid, sourced "From dosai_list_projects"), giving 100% schema coverage. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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 ("Read-only list of the DOS AI bot's functions") and then defines what a function actually is — saved settings the bot follows in its own chats, with concrete examples (Google Calendar booking, owner notification, Sheet write, webhook call). This distinguishes it from execution-oriented siblings such as dosai_list_function_runs without the agent needing to open any schema.

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?

Explicitly frames the correct mental model for use: these are data, not operations, and "no tool here executes a function," which steers the agent away from expecting execution semantics. It does not name a specific alternative to use for execution history or function runs, so there is no full when/when-not routing, but the usage context is clear.

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