Skip to main content
Glama

Outreach Path to Target

get_outreach_path
Read-onlyIdempotent

[Read · free] Given a target person, find the shortest warm-intro path through your engager network. Walks coworker (shared current company) + alumni (shared past company / school) edges. Up to 3 hops. Paths only exist where job history is on file, and engagers collected from reactions/comments usually have none: the response's coverage says how many candidates (the target, and engagers tied to the target's companies) have job history, and when missing data may hide paths _meta.next_step names enrich_people with the exact person_ids to pass and its credit cost. Pure DB read — no LinkedIn pull, no credits charged.

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_outreach_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax paths to return (default 10)
max_hopsNoMax path length (1=direct, 2=one intermediate, 3=two intermediates). Default 2.
target_person_idNoTarget — people.id UUID
target_linkedin_urlNoTarget — LinkedIn URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, but the description adds substantive context beyond them: 'pure DB read — no LinkedIn pull, no credits charged', the sparse-data caveat about engagers gathered from reactions/comments, and the `coverage` field that quantifies missing history. It does not describe the shape of a returned path (hop ordering, confidence), which is the one behavioral gap.

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 core capability is front-loaded in the first sentence, followed by edge types, hop ceiling, then the data-coverage caveat and remediation. Dense but every clause carries information; the final sentence is slightly redundant with the annotations' read-only signal.

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?

With no output schema, the description usefully names two response fields (`coverage` and `_meta.next_step`) and explains how to act on them, which is exactly what an agent needs to interpret a thin result. For a 4-parameter, no-write tool this is nearly complete; only the structure of the returned path list is left implicit.

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 100%, so limit, max_hops and the two target selectors are already documented at the field level. The description reinforces hop semantics ('up to 3 hops') but adds no format or precedence guidance beyond the schema, e.g. what happens if both target_person_id and target_linkedin_url are supplied. Baseline 3 is appropriate.

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: 'find the shortest warm-intro path through your engager network', and names the edge types it walks (coworker, alumni) plus the hard 3-hop ceiling. An agent can distinguish this from siblings like get_alumni_engagers or get_target_warmth_brief without opening either schema.

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 clear condition for when the tool fails to produce results ('paths only exist where job history is on file') and explicitly routes the agent to enrich_people via `_meta.next_step` when coverage is low, including the credit cost. It does not contrast against sibling path/warmth tools such as get_target_warmth_brief, so it stops short of full alternative guidance.

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