Skip to main content
Glama

Admin Substitute

by com.adminsubstitute

invoicing.chase

Find and chase overdue invoices. GET mode (no jobId): returns all overdue invoices with days overdue, chase level (friendly/firm/final), and total $ outstanding. SEND mode (with jobId + tone): sends a payment reminder via email (+ optional SMS) with 3-tier escalation — friendly (7+ days), firm (14+ days), final (30+ days). Includes Stripe payment link if connected. Each chase sent is logged and tracked for recovery metrics. The single most revenue-generating tool — 60-70% of friendly reminders result in payment within 48 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toneNoChase escalation level. Required when sending (with jobId).
jobIdNoJob ID to chase. Omit to list all overdue invoices instead.
sendSmsNoAlso send SMS reminder (default true if phone available).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate mutability (readOnlyHint=false), and the description confirms sending emails/SMS, logging, and tracking recovery. It adds context like Stripe payment link and 48-hour recovery metrics. No contradiction with annotations.

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?

The description is detailed but front-loaded with the core purpose. Each sentence adds value (modes, escalation, revenue impact). Could be slightly more structured with bullets, but overall concise given the complexity.

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?

The description covers both modes, escalation details, output format (days overdue, chase level, total outstanding), and side effects (logging, tracking). With an output schema present, the description is thoroughly complete.

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 baseline is 3. The description adds meaning: explains tone as escalation level, jobId as mode switch, sendSms default behavior. This goes beyond the schema's enum and type constraints.

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 the tool finds and chases overdue invoices, with two distinct modes (GET and SEND). It specifies the resource (invoices) and actions (list, send reminders), differentiating it from siblings like invoicing.recovery or comms.send_email.

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?

The description explains when to use GET mode (list overdue) vs SEND mode (with jobId and tone). It provides escalation levels and their thresholds. However, it does not explicitly exclude cases where alternative tools (e.g., comms.send_email) might be preferred.

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

All Admin Substitute toolsInspect
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