Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Log interaction

log_interaction
Idempotent

Record calls, emails, SMS messages, visits, and notes on a lead to track conversation facts; pass an idempotency key on retries.

Instructions

Record a call, email, SMS, visit, or note on a lead. Summary should be the facts of the conversation, not a guess. Pass an idempotencyKey on retry. Omitting occurredAt stamps the server clock, and that default is not part of the idempotency hash.

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>",
      "channel": "<channel>",
      "direction": "<direction>",
      "summary": "<summary>"
    },
    "name": "log_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYes
channelYes
summaryYesWhat was said. Facts only.
directionYes
occurredAtNoWhen it happened. Default is the server clock.
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes clearly beyond the annotations by disclosing a non-obvious interaction: omitting occurredAt stamps the server clock and that default is excluded from the idempotency hash, which directly affects retry semantics. The idempotentHint annotation is explained rather than merely restated. It still omits what happens on a duplicate lead, auth/permission requirements, and any side effects on lead state.

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 tight sentences with no filler; the core action comes first, then content guidance, then the retry and timestamp mechanics. Every clause carries operational information.

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 mutation tool with no output schema and 6 parameters, the definition covers the action, required content, idempotency, and timestamp default — enough to call it correctly. Missing are return shape and side effects on the lead, which the annotations cannot supply since no output schema exists.

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?

Schema coverage is only 33%, but the description compensates for precisely the ambiguous parameters: summary (facts only), occurredAt (server clock default), and idempotencyKey (use on retry). The remaining parameters (leadId, channel, direction) are self-evident from names and enum values, so the residual gap is small.

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 ("Record") plus the resource and enumerates the accepted channels (call, email, SMS, visit, note) on a lead, so the agent knows exactly what this does. It does not name a sibling it might be confused with (e.g. update_lead or schedule_follow_up), so it stops short of full disambiguation.

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 guidance for two parameters — retry behavior ("Pass an idempotencyKey on retry") and content quality ("facts of the conversation, not a guess") — which is genuinely useful. It never says when to choose this over update_lead or schedule_follow_up, or what preconditions exist (must the lead already exist?), so usage is only implied at the tool-selection level.

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