Skip to main content
Glama

Outreach sequence

parserail_outreach

Turn an enriched lead and your product details into a personalized outreach sequence that references why the prospect is a fit. Uses account credits per call.

Instructions

An enriched lead plus what you sell → a personalized outreach sequence that references what actually makes them a fit. Costs credits from the account wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadYesWho you're writing to, an enriched profile (e.g. /v1/enrich output) or notes.
stepsNo
senderNo
channelNo
productYesWhat you sell and the value proposition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.5

TDQS

B3.4/5.0
Behavior4/5

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

The description adds a material behavior not visible in annotations: 'Costs credits from the account wallet.' It also communicates that output is personalized based on lead fit, which is useful beyond the openWorldHint flag. Nothing contradicts the annotations.

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?

The description is a single, scannable sentence that conveys the core operation and a key side-effect. There is no filler and the main information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, including an undocumented nested sender object and an enum channel, plus no output schema, the description leaves significant gaps. It never explains what steps/sender/channel mean or what the sequence output looks like, so the definition is not complete enough for a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%: lead and product have descriptions, but steps, sender, and channel are undocumented. The description explains lead ('enriched profile') and product ('what you sell and value proposition') but does nothing to clarify the missing parameters, so it only partially compensates.

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 clearly explains the transformation: an enriched lead plus product information produces a personalized outreach sequence. It goes beyond the title 'Outreach sequence' and distinguishes this as the outreach-specific tool among the parserail siblings, though it does not explicitly contrast with any alternative.

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?

The arrow notation and 'what you sell' imply this is used when an agent has an enriched lead and a value proposition and needs personalized outreach. However, it gives no explicit guidance on when to choose this over a sibling tool, no exclusions, and no conditions for channel/steps.

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