Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

List due follow-ups

list_due_follow_ups
Read-onlyIdempotent

Retrieve scheduled follow-ups that are due now or overdue, ordered soonest first, to build a front desk call list.

Instructions

List scheduled follow-ups whose dueAt is at or before asOf (default: server clock). Ordered soonest first. This is the front desk call list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_due_follow_ups"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoInclude follow-ups due at or before this instant. Default is the server clock.
limitNoDefault 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds useful behavior – inclusive boundary on dueAt, soonest-first ordering, server-clock default – but says nothing about return shape, truncation at the 200 cap, or how the caller knows results were cut off.

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, each doing work: filter predicate, ordering, and use-case framing. Front-loaded and free of padding.

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 read-only listing tool with full schema coverage and annotations, the description covers selection semantics adequately. Minor gap: nothing says whether the response is paged or capped at limit, which matters for a call-list workflow with a 200 maximum.

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 both parameters already document their defaults in-schema, so the description's restatement of the server-clock default is redundant. The only added meaning is the inclusive nature of the boundary, which is marginal.

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 (list scheduled follow-ups) plus the exact filter predicate (dueAt <= asOf) and sort order (soonest first), so its scope is unambiguous. It does not explicitly separate itself from siblings like schedule_follow_up or set_follow_up_status, but the read/list nature is clear.

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?

"This is the front desk call list" gives an implied operational use case, which helps an agent recognize the daily-work scenario. There is no explicit when-not guidance and no named alternative for other follow-up queries, so guidance stays implicit.

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