Skip to main content
Glama
LeadFlow MCP

LeadFlow MCP

by kfairy9999

Search leads

search_leads
Read-onlyIdempotent

Search sales pipeline leads by name, service, city, email, phone, notes, stage, source, or score to find and filter matching records. Use sort and pagination to review ranked results.

Instructions

Search the pipeline. Text matches name, service, city, email, phone, and notes, case-insensitive for ASCII. Results are ranked inside the 500 most recently updated matches. When truncated is true, narrow the query. Scores are computed, not stored.

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": "search_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault updated_at, newest first.
textNoCase-insensitive ASCII match on name, service, city, email, phone, and notes.
limitNoPage size. Default 25.
stageNo
offsetNoDefault 0.
sourceNo
minScoreNoInclusive priority score floor. Applied after the scan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses two non-obvious behaviors: ranking only happens within the 500 most recently updated matches, and a truncated flag signals an over-broad query that should be narrowed. It also clarifies that scores are derived, not stored, which explains the score sort option. It does not describe pagination interaction with the 500-match window.

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?

Four short sentences, front-loaded with purpose followed by matching, ranking, and recovery guidance in priority order. There is minor redundancy with the schema's text field description.

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 carries the burden of explaining return values; it covers the truncated flag and ranking but never says what a result record contains or whether a total count is returned. For a 7-parameter search tool this leaves a meaningful gap, though the core call semantics are covered.

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 71%, so the schema already documents most parameters, and the description largely restates the text-match field list. It does add value by tying limit/offset behavior to the 500-match ranking window and by explaining that score is computed rather than persisted. The undocumented stage and source parameters are self-explanatory enums, so the 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 and resource ("Search the pipeline") and immediately defines what text matching covers, so an agent knows this is a text/filter search over leads. It never names a sibling such as get_lead or pipeline_summary, so the boundary with alternatives is left implicit.

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?

Usage is implied by the described filter and text semantics, plus a concrete recovery hint ("When truncated is true, narrow the query"). There is no explicit when-to-use versus the list/get siblings or when a non-search path would be better.

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