Skip to main content
Glama

Ready-made functions the bot can get

dosai_list_function_templates
Read-onlyIdempotent

Read-only catalogue of ready-made functions (saved settings) the owner can give the DOS AI bot, which then follows them by itself in its chats with clients: notify the owner (Telegram, email, WhatsApp), book into Google Calendar, read and write a Google Sheet, set tags, pause follow-ups, send photos, email the client. The catalogue is data: reading it executes nothing. For each: what it does, which settings it needs and what the owner must prepare. Also returns the bot's Google address: the owner shares a calendar or sheet with it before the function can work. Create one with dosai_create_function. 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>"
    },
    "name": "dosai_list_function_templates"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotent, but the description adds real context beyond them: "reading it executes nothing," an editor-role requirement, and the fact that each entry reports required settings plus the bot's Google address that must be shared before a function works. That prerequisite chain is exactly the kind of behavioral detail annotations cannot convey; only return-shape detail is absent.

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 read-only framing before the enumeration, and every clause (examples, data-not-execution, editor role, Google address) carries information. The mid-sentence list of function types is slightly dense and could be trimmed, but nothing is redundant.

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?

No output schema exists, so the description must describe the return value, and it does: per entry, what the function does and which settings the owner must prepare, plus the bot's Google address. Combined with the editor-role prerequisite and the read-only guarantee, an agent has everything needed to call this correctly and interpret the result.

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?

With one parameter at 100% schema coverage and a schema description pointing to dosai_list_projects, the schema already carries the semantics. The description adds nothing about project_id scope or what happens if it is wrong, so this sits at the baseline.

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: a read-only catalogue of ready-made function templates the owner can grant the bot, with concrete examples of what those functions do (notify, book, sheet, tags, photos, email). It also names the sibling for the opposite operation ("Create one with dosai_create_function"), so an agent can separate browsing templates from creating or listing already-installed functions.

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?

Clear context for use: consult this to learn what templates exist and what each requires, and it explicitly points to dosai_create_function for the write path. It does not explicitly exclude dosai_list_functions (existing configured functions), and the parenthetical "(saved settings)" blurs the template-vs-instance distinction, so a small ambiguity remains.

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