Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Get lead

get_lead
Read-onlyIdempotent

Read one lead with its priority score, interactions, and follow-ups before drafting outreach to keep replies within recorded facts.

Instructions

Read one lead with its priority score, interactions, and follow-ups. Use this before drafting outreach so the reply stays inside the recorded facts.

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>"
    },
    "name": "get_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds what comes back (scores, interactions, follow-ups) — genuinely useful since there is no output schema — but says nothing about missing/unknown lead IDs or any permissions.

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?

Two sentences, zero filler: the first states what is returned, the second states when to call it. Front-loaded and easy to scan.

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 single-parameter read tool with full annotation coverage, the definition covers purpose, payload, and usage rationale. The only meaningful omission is behavior for a non-existent or malformed lead ID.

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 would need to compensate, yet it says nothing about leadId. The name is self-explanatory and the schema carries pattern and length constraints, so the gap is mild rather than blocking.

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 a specific verb and resource ('Read one lead') and enumerates the payload the agent gets back (priority score, interactions, follow-ups). This makes it clearly distinct from list/search siblings by scope ('one lead'), though it never names an alternative explicitly.

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 concrete when-to-use rule: call it before drafting outreach so replies stay within recorded facts. It does not state exclusions or name which sibling to use for lead discovery instead, but the usage context is unambiguous.

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