Skip to main content
Glama

Get name-drop leads

get_name_drop_leads

Get the signed-in rep's next reverse name-drop leads.

A reverse name drop: the rep messages a prospect at an account they own and names a customer contact the prospect knows ("You and Andrew overlapped at the Marlins. He's at American Airlines Center now..."). Each lead has the prospect, the connector to name, where the two know each other from, the connector's customer today and what that customer uses the product for, plus the team's message template and how to write it.

Every lead returned is reserved for this rep, so no teammate is handed the same prospect. Call this once for the day's leads; if a call fails, calling again hands back the same leads. Draft each message from the lead's facts only, in the template's voice. When the rep sends one or decides not to, call record_name_drop with its lead_id.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many leads, up to the team's daily number (at most 25). Defaults to that number. Calling again the same day hands back the leads not yet reported on, then new ones.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Discloses the non-obvious side effect that each lead is reserved exclusively to this rep, which explains the readOnlyHint=false annotation and the non-idempotent retry semantics (repeat calls return unreported then new leads). It also describes the shape of the returned lead payload and the fact that drafting must stay within the lead's facts.

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?

Front-loaded with the outcome, then the concept, then the workflow; the example quote earns its space by making an uncommon lead type concrete. Slightly long for a single-parameter read tool, but no filler or repetition of annotations.

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?

Given a one-parameter tool with an output schema and annotations covering safety, the description supplies everything else an agent needs: the lead semantics, the reservation guarantee, retry behavior, drafting rules, and the follow-up sibling call. Nothing required to call it correctly is missing.

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 100%, and the schema already documents the count parameter's default, the 25 cap, and the re-call behavior. The description adds no further parameter-level detail (no format, ordering, or edge-case guidance) beyond repeating the daily-cadence idea, so the baseline 3 applies.

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 verb and resource (the signed-in rep's next reverse name-drop leads) and then defines the unfamiliar domain concept concretely, including what each lead contains. An agent can distinguish this from record_name_drop and from generic lead-fetching tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit calling cadence (once for the day's leads), failure behavior (calling again hands back the same leads), and a clear handoff rule: when the rep sends or declines, call record_name_drop with the lead_id. It also names the drafting constraint (use the lead's facts only, in the template's voice), leaving nothing to inference.

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.

Resources