Skip to main content
Glama

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

track_prospect

Log a signal from a prospect and update their temperature.

`signal` examples: booked_demo, asked_pricing, viewed_content, replied,
not_interested, too_expensive, no_time, competitor, ghosted_3_days,
ghosted_7_days, opted_out (they asked not to be contacted: ends the
relationship). Creates the prospect if new.

When you have the prospect's actual reply text, use `record_reply`
instead: it reads the reply and updates temperature, mode, objections and
do-not-contact for you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesThe prospect's handle or address on that channel, such as a Reddit username or an email address.
signalYesWhat happened: booked_demo, asked_pricing, viewed_content, clicked_link, replied, not_interested, too_expensive, no_time, competitor, not_decision_maker, bad_timing, ghosted_3_days, ghosted_7_days or opted_out.
channelYesWhere you talk to them, such as "reddit", "twitter" or "email". The handle and channel together identify the prospect.
mission_idNoOptional. The mission they came from, from get_missions.
product_idNoOptional. The product they are a prospect for, from get_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / channel / description
      Added value: +"Where you talk to them, such as \"reddit\", \"twitter\" or \"email\". The handle and channel together identify the prospect."
    • addedInput schema / properties / handle / description
      Added value: +"The prospect's handle or address on that channel, such as a Reddit username or an email address."
    • addedInput schema / properties / mission_id / description
      Added value: +"Optional. The mission they came from, from get_missions."
    • addedInput schema / properties / product_id / description
      Added value: +"Optional. The product they are a prospect for, from get_products."
    • addedInput schema / properties / signal / description
      Added value: +"What happened: booked_demo, asked_pricing, viewed_content, clicked_link, replied, not_interested, too_expensive, no_time, competitor, not_decision_maker, bad_timing, ghosted_3_days, ghosted_7_days or opted_out."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false), so the description only needs to add what they don't cover. It does: the tool creates the prospect if new (upsert semantics), and opted_out terminates the relationship. It does not describe the response payload, but that is a minor gap given annotation coverage.

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?

Three short blocks, front-loaded with the core action, then signal semantics, then the routing rule to record_reply. Every sentence earns its place; no filler.

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 5-param mutation tool with no output schema, the description covers the important behavioral facts (upsert creation, terminal signal, sibling routing). It stops short of noting that duplicate signals are not idempotent or what the call returns, leaving a small gap an agent might want.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: it enumerates signal values and interprets them (opted_out means the prospect asked not to be contacted and ends the relationship). That interpretation is genuine added value beyond the raw enum list.

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 (log a signal, update temperature) with a concrete scope, and explicitly distinguishes itself from record_reply. An agent can tell this apart from siblings like score_signal or record_reply 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?

Names the alternative (record_reply) and the precise condition that selects it: when the prospect's actual reply text is available. That is exactly the when-to-use/when-to-use-something-else guidance an agent needs.

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

All SignalPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources