HeyLead

Overview Schema Source Related Servers Discussions Admin

partner

Destructive

Track follow-ups with business partners, vendors, and investors. Manage a CRM-style pipeline and schedule automated email reminders on an escalating cadence.

Instructions

Track follow-ups with business partners, vendors, and investors.

Manages a CRM-style pipeline for non-prospect relationships (e.g., API
vendors, investors, co-founders). Auto-sends email reminders when
follow-ups are due using an escalating cadence (1, 3, 7, 14, 21 days).

Args:
    action: What to do:
        "add"      — Add a new partner to track (auto-schedules follow-ups)
        "list"     — Show all active partner follow-ups with due dates
        "update"   — Update partner info or add a note
        "complete" — Mark a partner follow-up as done (got what you needed)
        "snooze"   — Push the next follow-up by N days
        "cancel"   — Stop tracking this partner
    name: Partner's name (for 'add'). E.g., "Julien Crépieux".
    company: Company name (for 'add'). E.g., "Unipile".
    email: Partner's email (for 'add'). E.g., "partner@example.com".
    context: What you're following up about (for 'add').
    next_followup: Next follow-up date as YYYY-MM-DD (for 'add'). Defaults to tomorrow.
    partner_id: Partner ID (for 'update', 'complete', 'snooze', 'cancel').
    note: Add a note to the partner record (for 'update').
    days: Number of days to snooze (for 'snooze'). Default 7.

Input Schema

TableJSON Schema

Name	Required	Default
`days`	No
`name`	No
`note`	No
`email`	No
`action`	No	list
`company`	No
`context`	No
`partner_id`	No
`next_followup`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.375Sep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark the tool as non-read-only and destructive; the description adds important side-effect context by disclosing auto-sent email reminders with an escalating cadence (1, 3, 7, 14, 21 days). It also distinguishes 'complete' from 'cancel', though it does not specify whether cancel permanently deletes data.

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?

The description opens with a one-line purpose, adds a focused context paragraph, and then uses compact bullet-style Args entries. It is reasonably long but every line contributes necessary dispatch information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all nine parameters, all six actions, and the key side effect of auto-reminders, so an agent has enough to invoke the tool correctly. Since an output schema exists, not detailing return values is acceptable.

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 carries the full burden and provides an action-by-parameter mapping (e.g., partner_id for update/complete/snooze/cancel, next_followup defaulting to tomorrow). It explains defaults for next_followup and days, but 'days Default 7' conflicts with the schema's default of 0, preventing a perfect score.

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 purpose: tracking and managing follow-ups for non-prospect relationships, with clear examples of the target audience (API vendors, investors, co-founders). The explicit 'non-prospect relationships' framing distinguishes it from sibling tools like prospect.

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?

Gives a clear scope for when this tool applies and breaks down each action with its intent. It does not explicitly name an alternative tool for prospects or state exclusions, but the context is strong enough to route an agent correctly.

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