Skip to main content
Glama

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

get_pipeline

Read-onlyIdempotent

List the prospect pipeline sorted hottest-first.

Each prospect includes: id, handle, channel, temperature (0–100),
mode, last_signal, last_contact, and any recorded objections.

Modes (intent-based, not pure temperature):
  - nurture  — first-touch / no engagement yet. Educator persona,
               value-first messaging. Default for newly tracked
               prospects, regardless of starting temperature.
  - sales    — prospect has engaged (replied, clicked, asked).
               Consultant persona, qualify and build trust.
  - closing  — temperature ≥ 75 from sustained engagement. Closer
               persona, push for the concrete next step.
  - recovery — previously engaged and now cooled, OR explicit
               cooling signal (ghosted_*, not_interested, bad_timing).
               Re-engager persona, low-pressure re-open.
  - dead     — asked not to be contacted (a reply that opted out, or the
               opted_out signal). Never message them again;
               get_message_prompt refuses. Counted as do_not_contact.

Presentation: lead with the summary counts, then list the top
prospects as a numbered list with handle, temperature, mode, and
last signal. Do NOT introspect this response with shell commands —
the data is already structured and ready to summarise inline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: dead prospects are never to be contacted and are counted as do_not_contact, get_message_prompt will refuse them, and the response should not be introspected with shell commands.

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 purpose and return fields are front-loaded, and the mode list is long but earns its place by defining intent semantics the agent needs. Minor verbosity in the mode prose keeps it short of a 5.

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?

With no output schema, the description compensates by enumerating the returned fields (id, handle, channel, temperature, mode, last_signal, last_contact, objections) and even prescribing the presentation order. Nothing an agent needs to call or interpret this tool is missing.

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?

The tool takes zero parameters, which is the baseline-4 case. The description correctly adds no parameter guidance because none is needed.

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 ('List the prospect pipeline') plus the ordering rule ('hottest-first'). It also distinguishes itself from siblings by noting that get_message_prompt refuses dead prospects, so an agent can tell it apart from the messaging tools.

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 mode definitions imply when each prospect state applies and the dead-mode note hints at downstream tool behavior, but there is no explicit statement of when to call get_pipeline versus alternatives like track_prospect or score_signal. Usage is inferable rather than spelled out.

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