Skip to main content
Glama

co.build

Schedule an optional cobuild check-in email

schedule_installation_followup
DestructiveIdempotent

Schedule one installation check-in email for 1–72 hours from now, only after the user explicitly requests or agrees to that email. Delivery is to the connected account's verified email address. Scheduling authorizes that email, not publication of future feedback. An email already being sent or delivered cannot be recalled. Each report allows one check-in: retrying while pending returns the existing schedule without changing it; a sent or cancelled check-in cannot be scheduled again and returns followup_exists.

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": {
      "reportId": "<reportId>",
      "delayHours": "<delayHours>",
      "channel": "<channel>",
      "approved": "<approved>"
    },
    "name": "schedule_installation_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
approvedYes
reportIdYes
delayHoursYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description explains precisely why: one check-in per report, retries are non-destructive while pending, and a sent or cancelled check-in is permanently unavailable. It further discloses the delivery destination (connected account's verified email) and the irreversibility window (an email already being sent or delivered cannot be recalled), which the annotations cannot convey.

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 action and its precondition are front-loaded, and every sentence carries non-redundant information (consent, destination, scope-of-authorization, irreversibility, retry/error semantics). The final sentence is dense and runs two distinct behaviors together, which slightly hurts scanability but not substance.

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?

For a four-required-parameter mutation with no output schema, the description covers irreversibility, idempotent retry, and the followup_exists failure mode, but says nothing about what a successful call returns (schedule details? timestamp?) or where reportId should come from. An agent could still invoke it correctly, but it would not know what to expect back.

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?

With 0% schema description coverage the description must carry the load, and it does for most fields: delayHours is bounded as 1–72 hours, channel is fixed to email delivery at the verified address, and approved is explained via the explicit-consent precondition that justifies its const=true. The one gap is reportId, whose provenance (which report object it refers to) is never clarified.

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 ("schedule one installation check-in email") plus the temporal scope (1–72 hours from now) and the consent precondition. It is unmistakable against siblings such as cancel_installation_followup and publish_installation_report, since the description explicitly says scheduling authorizes the email, not publication of future feedback.

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?

"Only after the user explicitly requests or agrees to that email" is a hard, explicit precondition for invocation, which is exactly the guidance an agent needs. Retry behavior is also spelled out (pending retry returns the existing schedule; sent/cancelled returns followup_exists). It stops short of naming cancel_installation_followup as the alternative when a schedule must be undone, so it is not a full 5.

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