Admin Substitute

subcontractors.dispatch

Dispatch a job to a subcontractor. Sends SMS notification and creates a dispatch record for tracking. Subcontractor must be in "active" or "verified" status. Returns dispatch details.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	No	Link to existing job ID. Optional.
`amount`	No	Agreed payment amount in AUD. Optional.
`leadId`	No	Link to existing lead ID. Optional.
`sendSms`	No	Send SMS notification to subcontractor. Defaults to true.
`description`	Yes	Job description for the subcontractor. Required.
`scheduledDate`	No	Scheduled date (ISO 8601). Optional.
`subcontractorId`	Yes	ID of the subcontractor to dispatch to. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`dispatch`	No

TDQS

A4.5/5.0

Behavior4/5

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

Adds value beyond annotations by specifying SMS notification, record creation, and subcontractor status requirement. No contradictions.

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 sentences, all essential, no redundancy. Front-loaded with primary action.

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?

Covers core action, side effects, prerequisites, and return value. Output schema exists, so description is complete for an agent.

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%, but description adds context for sendSms (defaults true) and clarifies that description is for the subcontractor, enhancing understanding.

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?

Clearly states action ('dispatch a job to a subcontractor'), specifies side effects (SMS, dispatch record), and distinguishes from sibling tools like list, register, verify.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies when to use (dispatching a job) and includes prerequisite (subcontractor must be active/verified), but lacks explicit guidance on when not to use or direct comparison with siblings.

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.

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?