Skip to main content
Glama

Отправить письмо ещё раз

resend_quiz_email_log

Отправляет ещё раз письмо из журнала, которое не ушло (status = failed). В журнале появится новая запись.

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>",
      "log_id": "<log_id>"
    },
    "name": "resend_quiz_email_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_idYesID записи журнала (из get_quiz_email_log).
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the description need not restate mutation safety. It adds genuine context beyond them: only entries with status = failed qualify, and a new log record is created as a side effect — useful information for an agent deciding whether to retry.

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?

Two short sentences, front-loaded with the action and then the precondition. Nothing is repeated from the title or schema, and every sentence carries information the agent cannot get from structured fields.

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 action tool with full schema coverage and no output schema, the description covers the trigger condition and the resulting side effect. It does not say how a non-failed log_id is handled (error vs. no-op), a minor remaining 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 schema itself defines both log_id (with a pointer to get_quiz_email_log) and quiz_id. The description adds no further meaning about parameter values, formats, or constraints, 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?

The description names a specific verb and resource — resending an email from the log — and adds the qualifying condition 'status = failed'. It does not explicitly differentiate itself from the sibling resend_quiz_webhook_log, so an agent must infer the split from the resource noun alone.

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?

Usage is implied rather than stated: the agent can infer this is for re-sending a failed email, and the schema points to get_quiz_email_log as the source of log_id. It never says when NOT to use it or names an alternative tool, so guidance is only implicit.

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