Skip to main content
Glama

Пример письма себе

send_quiz_email_test

Отправляет пример письма вам (owner) или респонденту (client) в нынешнем виде — тема, шаблон, логотип, отправитель — с выдуманными ответами на почту аккаунта текущего пользователя. Тема с пометкой «Пример». Нужен опубликованный опрос. Не чаще раза в минуту.

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>",
      "type": "<type>"
    },
    "name": "send_quiz_email_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesowner — письмо вам о новом ответе, client — письмо респонденту.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive, so the safety profile is largely covered. The description still adds useful behavior beyond them: delivery goes only to the current user's account email, the subject is tagged «Пример», and there is a 1/minute throttle. It is silent on whether the send is recorded in the email log or counts against quotas, which limits it to adequate.

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 action and derived constraints in one dense sentence pair; every clause (what is rendered, where it goes, sample marking, prerequisite, throttle) carries information. Minor redundancy between the title and the «Пример» mention.

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 two-parameter test-send tool with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the remaining essentials: destination, prerequisite, and throttle. Return/confirmation behavior is left implicit, which is the only real gap.

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% and the enum already documents owner vs client, so the description adds little beyond restating the recipient distinction. Baseline 3 applies when the schema carries parameter meaning.

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+resource (sends a sample email) and immediately scopes it to the two recipient modes (owner vs client), so an agent can tell it apart from real send/resend tools. The added details — subject, template, logo, sender rendered as-is, fake answers — pin down exactly what 'sample' means.

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 hard prerequisite ("Нужен опубликованный опрос") and a rate limit (no more than once a minute), which are the practical conditions for calling it. It does not explicitly name an alternative (e.g. log/resend tools) or say when not to use it, so it falls short of a full when/when-not statement.

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