Skip to main content
Glama

Route search rows into outreach

spur_route_table_outreach
Destructive

Enroll each selected owner in the first reachable configured channel in order. Skips duplicate enrollments. This can start real outreach; approve the workflows and audience first.

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": {
      "table_id": "<table_id>",
      "routes": "<routes>",
      "order": "<order>",
      "confirm": "<confirm>"
    },
    "name": "spur_route_table_outreach"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
orderYes
routesYes
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
row_idsNo
table_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructive=true and openWorldHint=true, but the description adds real value by disclosing that this sends actual outreach messages and that duplicate enrollments are skipped. The "first reachable channel in order" rule is a genuine behavioral detail the schema does not convey. It stops short of describing failure behavior when no channel is reachable or whether enrollment can be undone.

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?

Three short sentences, front-loaded with the core behavior and ending on the highest-risk warning. Dense and free of filler, though "first reachable configured channel in order" is compact to the point of ambiguity about what makes a channel reachable.

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?

For a destructive, open-world tool with a nested routes object, a required confirm guard, and almost no schema documentation, the description is thinner than the stakes warrant. The confirm-approval requirement is only carried by the schema field description, and there is no output schema, so the agent gets no picture of what a run returns or how partial failures are reported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% across 6 parameters, so the description must carry more weight than it does. It hints at row selection and at the routes/order interaction, but never explains table_id, the all flag, or how routes values are interpreted (template IDs?), leaving most parameters documented nowhere.

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 action (enroll owners), target (selected rows in a table), and mechanism (first reachable configured channel in order), which is far more informative than the name alone. It doesn't name a sibling it differs from, but the routing semantics distinguish it well enough from generic table/automation 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?

Gives a precondition ("approve the workflows and audience first") that effectively signals when this is safe to call. There is no explicit statement of when to use this versus siblings like spur_control_table_run or spur_create_search_automation, so the guidance remains implied rather than comparative.

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