Skip to main content
Glama
Sign In

fnlowl

by com.fnlowl
OverviewDiscussionsAdmin

Draft sequence

draft_sequence
Destructive

Create a sequence AS A DRAFT. Steps are either an email or a delay in days — a delay is its own step, so two emails can run back to back. A branch may be added at the end; its paths are evaluated first-match-wins, left to right, and a filter with field null always matches, so it only makes sense last. Filters can only test what a lead already carries: unsubscribed and quizTierLabel.

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": {
      "name": "<name>",
      "widgetId": "<widgetId>",
      "steps": "<steps>",
      "branch": "<branch>"
    },
    "name": "draft_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
stepsYes
branchYes
projectNoA project id from list_projects. Runs this call in that project instead of the connection default.
widgetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds substantial semantics beyond the annotations: delays are standalone steps allowing back-to-back emails, branch paths resolve first-match-wins left to right, and a null-field filter always matches so belongs last. It doesn't disclose what is returned or whether the draft is inert until activated, but the structural rules are genuinely valuable.

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 dense sentences, front-loaded with the draft constraint, then steps, then branch semantics. No filler; every clause conveys a rule the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a required-nullable widgetId, the description should say what widgetId means and what comes back (e.g. an id usable with activate_sequence). The nested steps/branch semantics are well covered, but these gaps leave an agent guessing.

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 only 20%, and the description richly compensates for steps and branch (filter fields, ordering, allowed values). However widgetId — required and nullable — is left completely unexplained in both schema and description, and name's role is never addressed.

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, resource and lifecycle state ('Create a sequence AS A DRAFT'), which implicitly routes the agent away from update_sequence and activate_sequence. It never names those siblings explicitly, so the differentiation is implied rather than stated.

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 draft framing hints that activation is a separate later step, but there's no explicit 'use this when' or exclusion against update_sequence/create_template. Usage is inferable but not stated.

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

All fnlowl 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