Soxoa Automation Planner

Estimate automation ROI

estimate_automation_roi

Read-onlyIdempotent

Estimates reclaimable team capacity and an illustrative payback period from caller-supplied workload figures. Requires people, weekly hours per person and loaded hourly cost; when automatable share or working weeks are omitted, the server uses 60% and 48. Payback is calculated only when an implementation cost is supplied. Returns weekly and annual hours reclaimed, annual capacity value, payback months, the assumptions used and a recommended next step. Results are planning estimates, not guaranteed savings or financial advice.

Input Schema

Name	Required	Description
`people`	Yes	Number of people supplied by the user.
`workingWeeks`	No	Working weeks per year, 1 to 52. Optional; defaults to 48 when omitted. An explicit value is used as given.
`automatableShare`	No	Fraction of repetitive time that can be reclaimed (0.6 means 60%). Optional; defaults to 0.6 when omitted. An explicit value is used as given.
`loadedHourlyCost`	Yes	Loaded hourly labor cost in the user's stated currency, supplied by the user.
`implementationCost`	No	Implementation cost in the same currency as the hourly labor cost. Optional; when omitted, no payback estimate is calculated.
`weeklyHoursPerPerson`	Yes	Weekly hours each person spends on this workflow, supplied by the user.

Output Schema

Name	Required	Description	Default
`status`	Yes
`assumptions`	Yes
`annualCapacityValue`	Yes
`recommendedNextStep`	Yes
`annualHoursReclaimed`	Yes
`weeklyHoursReclaimed`	Yes
`estimatedPaybackMonths`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / automatableShare / description

Previous value: -"Fraction of repetitive time that can be reclaimed (0.6 means 60%). Omit when the user supplies no value; the server defaults to 0.6. Preserve an explicit user value; do not invent a different percentage."New value: +"Fraction of repetitive time that can be reclaimed (0.6 means 60%). Optional; defaults to 0.6 when omitted. An explicit value is used as given."

changedInput schema / properties / implementationCost / description

Previous value: -"Implementation cost in the same currency as hourly labor cost. Omit unless supplied or approved by the user; omitted cost means no payback estimate."New value: +"Implementation cost in the same currency as the hourly labor cost. Optional; when omitted, no payback estimate is calculated."

changedInput schema / properties / workingWeeks / description

Previous value: -"Working weeks per year. Omit when the user supplies no value; the server defaults to 48. Preserve an explicit user value; do not substitute calendar weeks."New value: +"Working weeks per year, 1 to 52. Optional; defaults to 48 when omitted. An explicit value is used as given."

Changed9 schema fields changedOct 2, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / automatableShare / default
```
Added value: +0.6
```

addedInput schema / properties / automatableShare / description

Added value: +"Fraction of repetitive time that can be reclaimed (0.6 means 60%). Omit when the user supplies no value; the server defaults to 0.6. Preserve an explicit user value; do not invent a different percentage."

addedInput schema / properties / implementationCost / description

Added value: +"Implementation cost in the same currency as hourly labor cost. Omit unless supplied or approved by the user; omitted cost means no payback estimate."

addedInput schema / properties / loadedHourlyCost / description

Added value: +"Loaded hourly labor cost in the user's stated currency, supplied by the user."

addedInput schema / properties / people / description

Added value: +"Number of people supplied by the user."

addedInput schema / properties / weeklyHoursPerPerson / description

Added value: +"Weekly hours each person spends on this workflow, supplied by the user."

addedInput schema / properties / workingWeeks / default
```
Added value: +48
```

addedInput schema / properties / workingWeeks / description

Added value: +"Working weeks per year. Omit when the user supplies no value; the server defaults to 48. Preserve an explicit user value; do not substitute calendar weeks."

First observedSep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful operational detail beyond annotations: default automatable share and working weeks, conditional payback calculation, returned metrics, and a disclaimer that results are planning estimates rather than guaranteed savings or financial advice.

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 front-loaded with purpose, then covers required inputs, defaults, conditional payback, and output/disclaimer in a compact paragraph. It is appropriately sized for a six-parameter calculator, though slightly dense in places.

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?

Given the rich annotations, full schema coverage, and presence of an output schema, the description is complete enough for correct invocation. It covers required inputs, defaults, conditional behavior, return summary, and caveats without needing to explain every output field.

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 description coverage is 100%, so the schema already documents parameter meanings, defaults, ranges, and currency requirements. The description restates required parameters and default behavior but adds little semantic detail beyond the structured schema.

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?

The description states a specific verb and resource: estimating reclaimable team capacity and an illustrative payback period from caller-supplied workload figures. It is clear what the tool does, though it does not explicitly contrast itself with the sibling prioritize_automation_workflows tool.

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?

It specifies required inputs and conditions for output: people, weekly hours per person, and loaded hourly cost are required, while payback is calculated only when implementation cost is supplied. It gives clear invocation context but does not state when to choose this over the sibling tool or when not to use it.

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

All Soxoa Automation Planner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?