Skip to main content
Glama

Журнал писем опроса

get_quiz_email_log
Read-onlyIdempotent

Письма опроса за последние 30 дней, новые сверху: письма вам и респонденту, о записях, по правилам, сводки, события, напоминания. По каждому — кому, тема, ушло (sent) или нет (failed) и почему. Отвечает на «письма не приходят». Не ушедшее можно отправить ещё раз через resend_quiz_email_log.

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": {
      "quiz_id": "<quiz_id>"
    },
    "name": "get_quiz_email_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько записей, 20 по умолчанию, до 100.
offsetNoСколько пропустить с начала.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description adds real behavioral facts beyond that — a fixed 30-day lookback window, newest-first ordering, the per-record fields (recipient, subject, sent/failed status and reason), and the resend path for failures. It omits anything about volume limits or permissions, which keeps it below a 5.

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?

Four dense sentences with zero filler: scope and ordering first, then record contents, then the use case, then the alternative. Every clause carries information an agent needs to decide and to interpret the response.

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, the description takes on the job of describing returns and does it well (per-record recipient, subject, status, failure reason), plus the diagnostic framing and the resend follow-up. Only minor gaps remain, such as whether older-than-30-days data is reachable at all.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so limit and offset are already documented; the description contributes the one thing the schema cannot convey — that the result set is implicitly bounded to the last 30 days, which materially affects how pagination will behave. Baseline is 3, raised for that added constraint.

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 resource (quiz email log) with explicit scope and ordering: 'Письма опроса за последние 30 дней, новые сверху', then enumerates the categories of emails included (to you and the respondent, about responses, rules, digests, events, reminders). An agent can distinguish this from resend_quiz_email_log or get_quiz_email_settings without opening 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?

Gives a concrete triggering scenario — 'Отвечает на «письма не приходят»' — so the agent knows this is the diagnostic tool for missing-email complaints, and routes the follow-up action to resend_quiz_email_log for failed entries. It does not state an explicit when-not-to-use condition, 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