Skip to main content
Glama

Recent function calls

dosai_list_function_runs
Read-onlyIdempotent

The latest calls of one function by the bot: when, in which dialog, with what result. 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_list_function_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, max 50, default 20.
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
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description only needs to add context. It does add the editor-role authorization requirement and the shape of returned rows (timestamp, dialog, result), though it omits ordering ('latest' implies newest-first but is not stated) and pagination behavior beyond the limit param.

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?

A single front-loaded sentence describing output followed by a short permission clause; no filler or redundancy.

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 read tool with rich annotations and no output schema, the description covers scope, permissions, and the gist of returned data. Minor gaps remain around ordering and pagination, which the schema only partially addresses via limit/default 20.

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%, with project_id and function_id pointing at their own list tools and limit's default/max documented in the schema. The description contributes only the notion that function_id scopes the listing to one function, so the 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?

States a specific verb and resource ('latest calls of one function') and even previews the returned fields (when, dialog, result). It scopes results to a single function, which implicitly separates it from dosai_list_rule_runs, but never names that sibling or any other alternative.

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?

Use is implied: inspect recent executions of a given function. The 'Requires editor role' clause is a useful precondition, but there is no explicit when-not guidance and no routing to alternatives such as dosai_list_rule_runs or dosai_list_function_versions.

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