Skip to main content
Glama

generate_lead_funnel

Read-onlyIdempotent

Draft lead-funnel steps (qualification stages and scoring) from an agent prompt with AI. Returns the suggested steps only — save them with update_agent funnelConfig. Pass the agent prompt text; get it from get_agent if needed. Actions: generate — suggest funnel steps

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": {
      "action": "<action>",
      "agentPrompt": "<agentPrompt>"
    },
    "name": "generate_lead_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
actionYes
userNotesNoExtra guidance, e.g. what a hot lead means for this business.
agentPromptYesThe agent instructions to analyse.
existingStepsNoCurrent steps to refine instead of starting over.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses the critical behavioral trait beyond annotations: it drafts and returns suggested funnel steps only, and does not persist them; saving must be done separately via update_agent funnelConfig. This prevents an agent from assuming the tool writes the funnel. The annotations already cover safety and idempotency, and the description is consistent with them.

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?

The definition is front-loaded and efficient: the core purpose and persistence caveat come first, followed by practical guidance on obtaining the prompt. The trailing 'Actions: generate — suggest funnel steps' is redundant with the opening sentence and the action enum, slightly reducing conciseness.

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 read/draft tool with no output schema and high schema coverage, the description covers what it does, what it returns, and how to persist the output. It leaves minor details about mode, existingSteps behavior, and output structure to the schema, but an agent has enough to call it correctly.

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 high (80%), so the schema handles most parameter meaning. The description adds useful context for agentPrompt by directing the agent to fetch it from get_agent if needed, and it clarifies the single action value. It does not add detail for mode, userNotes, or existingSteps, which is acceptable given the schema descriptions.

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?

The description states a specific verb (Draft), a specific resource (lead-funnel steps including qualification stages and scoring), and the source (an agent prompt with AI). It also distinguishes the tool from the saving operation by saying it returns suggested steps only, so an agent can immediately tell it apart from update_agent.

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?

It gives clear context for when to use this tool and names alternatives for adjacent needs: get the prompt from get_agent and persist results with update_agent funnelConfig. It stops short of an explicit 'do not use when' statement, but the alternative guidance is sufficient for correct routing.

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