Skip to main content
Glama

Outil.io

List prospect follow ups

list_prospect_follow_ups
Read-only

Relances de prospection à faire : prospects dont la prochaine relance (nextFollowUpAt) est passée ou tombe avant until (AAAA-MM-JJ, défaut maintenant), les plus anciennes d’abord, avec dernier contact et note de suivi. Après chaque relance, update_record type prospects : lastContactedAt, nextFollowUpAt (vide = plus de relance), followUpNote.

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_prospect_follow_ups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
untilNo
searchIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: default `until` is now, result ordering is oldest-first, and empty nextFollowUpAt means no further follow-up. It says nothing about result volume, pagination, or what happens at the limit cap.

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?

Two dense sentences with the purpose and filter criteria front-loaded, followed by the workflow step. No filler, though the second sentence's field list is compressed enough to be slightly cryptic.

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?

With no output schema, the description should characterize returns; it partially does (last contact, follow-up note, ordering). Gaps remain on pagination/limit behavior and the meaning of searchId, which matter for a tool with three undocumented parameters.

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 carries the burden; it fully specifies `until` (AAAA-MM-JJ format, defaults to now) but leaves `limit` and `searchId` entirely unexplained, including the 1-200 range and what searchId scopes. 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?

The description names the resource precisely (prospects whose nextFollowUpAt is due or before `until`) and the verb (list), plus scope details like oldest-first ordering and the included fields (last contact, follow-up note). It never names a competing sibling, but no obvious alternative exists among the list_* tools, so an agent can still identify the right tool.

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?

It states the work context (follow-ups that are due) and prescribes the follow-up action: after each call, use update_record on type prospects with lastContactedAt, nextFollowUpAt and followUpNote. It does not give explicit when-not-to-use conditions or mention searchId-based scoping.

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.