Skip to main content
Glama

Draft outreach message

spur_draft_message
Destructive

Draft an email, SMS or direct-mail message with Spur's AI. Returns text only; nothing is sent. Pass owner_id/property_id to personalize with real owner and property data.

Uses 2 actions from the user's Actions pool. Use {{merge_fields}} like {{owner_first_name}} and {{property_address}} to keep it reusable (see resource spur://merge-variables).

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": {
      "channel": "<channel>",
      "prompt": "<prompt>",
      "confirm": "<confirm>"
    },
    "name": "spur_draft_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesWhat to write, e.g. "friendly first touch asking if they would sell, mention we close in cash"
channelYesWhich kind of message to draft
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
owner_idNoOwner to personalize for (from spur_find_owners)
property_idNoSaved property the message is about

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "const": true,
      +  "description": "Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "channel",
      -  "prompt"
      -]New value: +[
      +  "channel",
      +  "prompt",
      +  "confirm"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already disclose that the tool is non-read-only, non-idempotent, open-world, and marked destructive. The description adds meaningful context beyond that: it returns text only, sends nothing, consumes 2 Actions per call, and supports merge fields for reusable personalization. This is strong disclosure, though it does not explain persistence of the drafted message or further cost/rate-limit implications.

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?

The description is compact and front-loaded: the first sentence states the action, channels, and return/send boundary. The second paragraph adds cost and merge-field guidance without wasting words. Every sentence contributes useful information for invoking the tool correctly.

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?

For a five-parameter, open-world AI drafting tool with no output schema, the description covers the essentials: what it produces, that nothing is sent, that it consumes Actions, and how personalization and merge fields work. The schema already carries the approval semantics via confirm, so the description need not repeat them. It is complete enough for an agent to understand the tool's scope and side effects.

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 schema already documents all five parameters and the confirm approval requirement. The description adds value by explaining that owner_id and property_id personalize using real owner and property data, and by directing prompt usage toward {{merge_fields}} such as {{owner_first_name}}. That extra guidance justifies an above-baseline score.

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?

The description states a specific verb and resource: drafting an email, SMS, or direct-mail message with Spur's AI. It also clarifies the output boundary, 'Returns text only; nothing is sent,' which helps distinguish this from sending or delivery tools. It does not explicitly differentiate from sibling capabilities such as previewing a draft, so it stops short of a 5.

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?

It implies usage by describing drafting and personalization, and it warns that the tool consumes 2 actions from the user's Actions pool. However, it gives no explicit when-to-use versus when-not-to-use guidance and does not name sibling alternatives such as preview or retrieval tools. The confirm parameter's approval requirement is carried by the schema rather than the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources