Admin Substitute

workflows.trigger_invoice

Generate and send an invoice for a completed job. Auto-pushes to connected accounting software (Xero/QuickBooks/MYOB/FreshBooks), generates Stripe payment link, and notifies the customer via SMS. Full pipeline: invoice → accounting sync → payment link → customer notification → team alert.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	Job ID to invoice. Required. The job should be in Completed status with a linked quote for line items.
`dueInDays`	No	Payment due in N days from today. Defaults to 14.
`includePaymentLink`	No	Generate a Stripe payment link. Defaults to true if Stripe is connected.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No
`paymentUrl`	No	Stripe payment link URL
`invoiceTotal`	No	Invoice total in AUD

TDQS

A4.6/5.0

Behavior5/5

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

Discloses multiple side effects beyond annotations: auto-push to accounting, Stripe link generation, SMS notification to customer, and team alert. Annotations (readOnlyHint=false) align with mutating behavior; no contradiction.

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 with no fluff. First sentence immediately states action and key behaviors; second summarizes pipeline. Front-loaded and efficient.

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?

Covers purpose, pipeline steps, prerequisites, and important behaviors. Does not mention error handling or dependency on accounting connection, but output schema likely fills gaps. Good overall completeness.

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% with descriptions. The description adds business context (e.g., the pipeline steps) that helps interpret parameters, though it largely restates schema defaults. Adds value beyond raw 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?

States 'Generate and send an invoice for a completed job' with specific verb and resource. The 'Full pipeline' detail distinguishes it from sibling invoicing tools like invoicing.generate or invoicing.chase, making the purpose unique and clear.

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?

Includes prerequisite 'The job should be in Completed status with a linked quote for line items' from the schema, implying when to use. However, lacks explicit guidance on when NOT to use (e.g., when accounting integration is absent) and does not name alternative tools. Still helpful.

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?