Skip to main content
Glama

Event log

dosai_list_logs
Read-onlyIdempotent

What the bot and the platform did: messages processed, functions called, errors. Filter by category (all | telegram | whatsapp | error | processed), text search and dates. Use it to explain a failure.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, max 50, default 20.
searchNo
date_toNo
categoryNo
date_fromNo
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered by structured data. The description adds useful content-type context (messages, function calls, errors) but says nothing about retention windows, ordering of results, or how far back the log goes — behavior an agent would want before relying on it for debugging.

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?

Three tight sentences, front-loaded with what the log contains before the filter options and the use case. The only waste is echoing the full category enum ('all | telegram | whatsapp | error | processed'), which the schema already enumerates.

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

Completeness3/5

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

For a six-parameter tool with a third of parameters undocumented and no output schema, the description covers the essential shape but not the return side: what an event row contains, how paging behaves beyond the limit param, and result ordering are all unstated. Adequate but with clear gaps for a debugging-oriented tool.

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 only 33%, so search, date_from and date_to carry no schema text, and the description must compensate. It does map the three filter axes (category, text search, dates) to intent, but it merely restates the enum values already in the schema and gives no detail on whether date bounds are inclusive, what fields the text search scans, or how category interacts with the other filters.

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 concrete verb-and-resource picture: an event log of 'messages processed, functions called, errors' covering what the bot and platform did. That distinguishes it from data-oriented siblings like dosai_list_conversations or dosai_list_leads, though it never names the nearest neighbors (dosai_list_function_runs, dosai_list_integration_failures) that an agent might confuse it with.

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 it to explain a failure' is real when-to-use guidance tying the tool to a debugging task, which is more than most definitions offer. However, there is no when-not guidance and no named alternative (e.g., a function-runs or integration-failures list) for cases where the agent wants details on a specific failing execution rather than a flat event feed.

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