Skip to main content
Glama
Sign In

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

record_message

Record a message you drafted as sent to the prospect.

Use after `get_message_prompt`. Daily send cap still applies.

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": {
      "prospect_id": "<prospect_id>",
      "message": "<message>"
    },
    "name": "record_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
tacticNoOptional one-phrase label of the approach, as in the schema get_message_prompt returned.
messageYesThe message you sent, word for word.
next_stepNoOptional. What to do after this message, as in the same schema.
prospect_idYesThe prospect's id, from get_pipeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / message / description
      Added value: +"The message you sent, word for word."
    • addedInput schema / properties / next_step / description
      Added value: +"Optional. What to do after this message, as in the same schema."
    • addedInput schema / properties / prospect_id / description
      Added value: +"The prospect's id, from get_pipeline."
    • addedInput schema / properties / tactic / description
      Added value: +"Optional one-phrase label of the approach, as in the schema get_message_prompt returned."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive behavior. The description usefully adds the daily send-cap constraint, which annotations cannot express, but it does not say what happens when the cap is hit or whether repeated calls create duplicate records despite idempotentHint=false.

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?

Two short sentences that front-load the action and then the prerequisite and constraint. 'Daily send cap still applies' is slightly elliptical but earns its place as the only behavioral caveat.

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 mutation tool with no output schema, the description covers the prerequisite, the side effect (marks a message as sent) and the rate cap, while annotations cover the safety profile. It stops short of describing duplicate handling or downstream pipeline effects.

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 coverage is 100% with all four parameters described, so the schema carries the parameter burden. The description adds a small amount by tying 'tactic' and 'next_step' back to the schema returned by get_message_prompt, but no field formats or constraints beyond that.

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?

States a specific verb and resource – recording a drafted message as sent to a prospect – which is clear on its own. It does not distinguish itself from the sibling mark_sent, so an agent must guess which of the two records a send in which situation.

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 an explicit prerequisite ('Use after get_message_prompt') and an operating constraint ('Daily send cap still applies'), which is real sequencing guidance. It omits any when-not guidance and says nothing about how it differs from mark_sent or upload_draft.

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