Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Set follow-up status

set_follow_up_status
Idempotent

Set a follow-up to scheduled, done, or cancelled so done and cancelled items drop from due lists; repeating the same status is safe.

Instructions

Mark a follow-up scheduled, done, or cancelled. Setting the same status again is safe. Done and cancelled items drop out of list_due_follow_ups.

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": {
      "followUpId": "<followUpId>",
      "status": "<status>"
    },
    "name": "set_follow_up_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
followUpIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so 'setting the same status again is safe' mostly restates structured data. However, it goes beyond annotations by disclosing a real side effect: done and cancelled items drop out of list_due_follow_ups, which is exactly the consequence an agent needs to anticipate.

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 action and permitted values, followed by the idempotency note and the downstream consequence. No filler or redundant phrasing.

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 mutation with full annotation coverage and no output schema, the definition covers the action, allowed states, idempotency, and the visibility side effect. It stops short of clarifying whether transitions are unrestricted (e.g., done back to scheduled) or how the follow-up id is obtained.

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 0%, so the description must carry parameter meaning; it does list the three status values, but that duplicates the enum already in the schema and it says nothing about where followUpId comes from (e.g., from list_due_follow_ups) or what an invalid id does. Partial compensation only.

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 ('Mark') and resource ('a follow-up') and enumerates the three target states, so the operation is unambiguous. It does not explicitly contrast itself with schedule_follow_up or explain the relationship to creation, so it falls short of full sibling differentiation.

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?

The description implies when the tool is used (transitioning an existing follow-up's state) and notes the downstream effect on list_due_follow_ups, but gives no explicit when-not guidance or pointer to the alternative tool for creating/rescheduling a follow-up. Usage is inferable rather than stated.

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