Skip to main content
Glama
Sign In
INFATON MCP35

INFATON MCP35

Official
by infaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_event_log

Retrieve log entries filtered by date range, event type, and user. A key diagnostic tool for system analysis.

Instructions

Получить записи журнала регистрации с фильтрацией по периоду, событию и пользователю. Ключевой инструмент диагностики.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_event_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoКоличество записей (по умолчанию 100)
period_toNoКонец периода YYYYMMDD (по умолчанию сегодня)
period_fromNoНачало периода YYYYMMDD (по умолчанию сегодня)
user_filterNoФильтр по пользователю (необязательно)
event_filterNoФильтр по событию (необязательно)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only describes retrieval and filtering but does not disclose behavioral traits such as whether it is read-only, performance implications, authentication requirements, or any side effects.

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?

The description is brief (two sentences) and front-loaded with purpose. However, the second sentence 'Ключевой инструмент диагностики' adds minimal new information and could be integrated or omitted.

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?

Given the simplicity (5 params, no required fields, no output schema, no annotations), the description adequately covers the purpose and filtering. However, it lacks details on default behavior of parameters (e.g., limit defaults) and output format.

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?

Input schema has 100% parameter description coverage, and the description adds no additional meaning beyond what is already in the schema. Baseline of 3 is appropriate.

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?

The description clearly states that the tool retrieves event log records with filtering by period, event, and user, and labels it as a key diagnostic tool. This distinguishes it from sibling tools like get_exchange_log, providing specific verb-resource-purpose clarity.

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?

The description implies use for diagnostics but does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. With many sibling 'get_' tools, guidance on selection is lacking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools