Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Reschedule email

update_scheduled_email
Idempotent

Change the send time of a scheduled email via PATCH /emails/:id; non-scheduled emails return a validation error. Requires a full-access key; a past time sends immediately.

Instructions

PATCH /emails/:id. Changes the send time of an email whose status is still "scheduled"; any other status returns 422 validation_error. The new time is ISO 8601, up to 30 days ahead. WARNING: a time in the past sends the email immediately. Needs a full-access key.

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": {
      "id": "<id>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "update_scheduled_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe email id returned when it was sent.
scheduled_atYesNew ISO 8601 send time, up to 30 days ahead, e.g. "2026-10-21T09:00:00Z". A time in the past sends immediately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, idempotentHint=true and destructiveHint=false, but the description adds real value beyond them: the 422 on wrong status, the 30-day horizon, and the full-access key requirement. The most consequential behavior, that a past timestamp fires the email immediately, is a genuine side effect worth flagging, though the description doesn't say whether the change is reversible or what a successful response returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly four short sentences, each carrying distinct information (route, status guard, format/horizon, past-time warning, auth) and front-loaded. However, the WARNING fragment is clipped to the point of being terse, and the parameter-level facts duplicate the schema rather than consolidating.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers eligibility, validation failure mode, value constraints, side effect and auth scope. An agent has everything needed to call it correctly and to anticipate the failure case.

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 coverage is 100% and the schema descriptions already state the ISO 8601 format, the 30-day cap and the past-time behavior, so the description largely restates rather than extends them. It adds no syntax or edge-case detail (e.g. timezone handling) beyond what the schema provides.

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 and resource ("Changes the send time of an email") plus the HTTP route and the guard condition (status must be "scheduled"), which cleanly separates it from siblings like cancel_email or send_email.

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 an explicit when-not rule (any status other than "scheduled" returns 422 validation_error) and a prerequisite (full-access key), so the agent can decide eligibility before calling. It stops short of naming a sibling alternative for non-scheduled emails, which would have earned a 5.

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