Skip to main content
Glama
Sign In

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

draft_mission

Get the drafting payload for a single mission so you can write the reply.

This is a working payload, not a display payload — it intentionally
contains the product positioning, lead text, scoring breakdown, and
response schema your draft must follow. Use it to write the draft;
do NOT dump the full payload back to the user.

Workflow:
    1. Call this with the mission_id.
    2. Compose a reply that fits the role/tone in `context.strategy`.
    3. Call `upload_draft(mission_id, draft, reasoning)` with your draft.
    4. If the lead is clearly not a buying signal, skip drafting and
       call `reject_mission(mission_id, rejection_reason)` instead.

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": {
      "mission_id": "<mission_id>"
    },
    "name": "draft_mission"
  }
}

Input Schema

NameRequiredDescriptionDefault
mission_idYesThe mission's id, from get_missions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mission_id / description
      Added value: +"The mission's id, from get_missions."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, openWorldHint=false and destructiveHint=false, so the mutation/idempotency profile is already covered. The description adds real value beyond that by disclosing the payload's nature ('working payload, not a display payload') and an explicit behavioral constraint ('do NOT dump the full payload back to the user'), though it does not state auth or rate-limit behavior.

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?

Purpose and the key 'working not display' warning are front-loaded, followed by a compact numbered workflow. Every sentence earns its place and there is no padding or redundancy.

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?

No output schema exists, yet the description enumerates the payload contents (product positioning, lead text, scoring breakdown, response schema) the agent must use, and supplies the full drafting lifecycle. Nothing essential for correct invocation 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?

With a single parameter at 100% schema coverage, the schema already documents mission_id (including its provenance from get_missions). The description adds minor value by confirming the call signature ('Call this with the mission_id') and tying it into the workflow, so it supplements rather than repeats the schema.

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 ('Get the drafting payload for a single mission') and immediately clarifies its downstream purpose ('so you can write the reply'). It also distinguishes itself from display-oriented data and from sibling tools by name, so an agent can tell what this does versus upload_draft or get_missions.

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?

Provides an explicit numbered workflow covering when to call it, what to do next (upload_draft), and the concrete alternative (reject_mission when the lead is not a buying signal). The when-to-use and when-to-skip conditions are both 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