Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Schedule follow-up

schedule_follow_up
Idempotent

Schedule a follow-up reminder for a lead at a chosen due date or immediately if the date is past; add an idempotency key to safely retry the request.

Instructions

Schedule a follow-up for a lead. dueAt may be in the past, which makes it due immediately. Pass an idempotencyKey on retry.

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": {
      "leadId": "<leadId>",
      "dueAt": "<dueAt>",
      "reason": "<reason>"
    },
    "name": "schedule_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueAtYesAllowed in the past. Past items show up in list_due_follow_ups immediately.
leadIdYes
reasonYes
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write and idempotent profile, and the description usefully adds that past dueAt values are accepted and surface immediately in list_due_follow_ups, plus the retry convention. It still omits what is returned and who may schedule for a given lead, so it is strong but not complete.

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?

Three short sentences, front-loaded with the core action, followed by the two edge cases an agent would otherwise get wrong. Nothing is repeated from the annotations or schema verbatim.

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 simple four-parameter mutation with no output schema, the description covers the two behavioral traps (past dates, retries) adequately. It leaves the semantics of leadId and reason and the shape of the result unaddressed, which an agent may need before trusting the call.

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 only 25%, with leadId and reason documented nowhere. The description compensates partially by explaining past-dated dueAt and when to supply idempotencyKey, but the two remaining parameters carry no semantic guidance in either place.

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?

States a specific verb and resource ('Schedule a follow-up for a lead'), which is enough to separate it from siblings like set_follow_up_status and list_due_follow_ups. It does not explicitly name or contrast those alternatives, so it stops short of a 5.

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?

Gives concrete conditional guidance for two cases: a past dueAt means the follow-up is due immediately, and a retry should carry an idempotencyKey. It never says when to choose this over set_follow_up_status or log_interaction, so usage is implied rather than fully routed.

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