Admin Substitute

workflows.instant_response

Send an instant SMS + optional WhatsApp follow-up to a new lead within 30 seconds. Fires branded SMS templates for Growth+ plans.

Input Schema

TableJSON Schema

Name	Required	Description
`leadId`	Yes	Lead ID. Required.
`customMessage`	No	Override the auto-generated response message. Optional.
`includeWhatsApp`	No	Send WhatsApp follow-up if connected. Default true.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`smsSent`	No
`success`	No
`whatsAppSent`	No
`templatesSent`	No

TDQS

A4/5.0

Behavior4/5

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

Annotations indicate non-destructive, non-idempotent, and open-world behavior. The description adds useful context: 30-second guarantee, branded templates, and optional WhatsApp. Does not contradict annotations.

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?

Two sentences, both substantive. No redundant information. Front-loaded with key action and timing.

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?

Given the tool's simplicity and presence of output schema, the description covers core behavior. Missing mention of error handling or idempotency considerations, but not critical for an instant response tool.

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 has 100% coverage for all three parameters. Description adds 'optional WhatsApp follow-up' aligning with includeWhatsApp but does not enhance meaning of leadId or customMessage beyond 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?

The description clearly states it sends an instant SMS and optional WhatsApp to a new lead within 30 seconds, with branded templates for Growth+ plans. This distinguishes it from siblings like comms.send_sms by specifying target audience and timing.

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 description implies usage for new leads needing immediate response but does not explicitly state when to use this tool versus alternatives like comms.send_sms. No exclusion guidance or when-not-to-use is provided.

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

All Admin Substitute tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools have distinct resource+action naming (e.g., leads.create, jobs.list), but some overlap exists in analytics tools (dashboard, detailed, financials) and workflow automations (process_lead vs google_ads_pipeline). Descriptions clarify purposes, so slight confusion is possible but limited.

Naming Consistency5/5

All tools follow a consistent `domain.action` pattern (e.g., leads.create, billing.status). No mixing of camelCase or snake_case. Even complex names like lifecycle.assess or scaling.readiness_score adhere to the convention.

Tool Count1/5

95 tools is far beyond typical well-scoped servers (3-15). While the server aims to cover an entire business management platform, this volume is overwhelming for an agent, making selection and memory difficult.

Completeness5/5

The tool surface is exceptionally comprehensive, covering formation, hiring, compliance, funding, leads, quotes, jobs, invoicing, payments, marketing, analytics, integrations, webhooks, workflows, and more. Almost no obvious gaps in the lifecycle of running a trade business.

Resources

Need Help?