Soxoa Automation Planner

Estimate automation ROI

estimate_automation_roi

Read-onlyIdempotent

Estimate reclaimable team capacity and illustrative payback from user-supplied workload assumptions. Omit unsupplied optional inputs: the server defaults to 60% automatable share and 48 working weeks. Ask for missing people, weekly hours per person, or loaded hourly cost; do not invent assumptions. Use for operational planning, not guaranteed savings or financial advice.

Input Schema

TableJSON Schema

Name	Required	Description
`people`	Yes	Number of people supplied by the user.
`workingWeeks`	No	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.
`automatableShare`	No	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.
`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 hourly labor cost. Omit unless supplied or approved by the user; omitted cost means no payback estimate.
`weeklyHoursPerPerson`	Yes	Weekly hours each person spends on this workflow, supplied by the user.

Output Schema

TableJSON 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.

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 this as a safe read-only, idempotent, closed-world computation, so the safety profile is covered. The description adds meaningful behavior beyond that: the server-side defaults (60% automatable share, 48 working weeks), the requirement to preserve user-supplied values, the "do not invent assumptions" guardrail, and the illustrative-not-guaranteed framing. It does not describe output shape, though the output schema covers that.

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?

Four tight sentences, front-loaded with the purpose before the operational rules and the disclaimer. Every sentence carries actionable content, with only minor overlap between the default-value sentence and the schema defaults.

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?

For a read-only estimation tool with a rich output schema and 100% schema coverage, the description supplies everything an agent needs: the input contract, default behavior, how to handle missing values, and the interpretive limits of the result. Return values are appropriately left to the output schema.

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 every parameter including defaults, bounds, and the omit-vs-preserve rule is already documented in the schema. The description restates the default values for automatableShare and workingWeeks but adds no new syntax or format meaning. This is the baseline 3 where the schema does the heavy lifting.

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: "Estimate reclaimable team capacity and illustrative payback from user-supplied workload assumptions." An agent immediately knows this produces a capacity/payback estimate from supplied workload inputs. It does not, however, name or contrast itself with the sibling prioritize_automation_workflows, so differentiation is left to inference.

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 gives clear usage context ("Use for operational planning") and an explicit exclusion ("not guaranteed savings or financial advice"), plus operational rules for when to omit optional inputs versus ask for missing required ones. The one gap is that it never points to the sibling tool as an alternative for prioritization tasks.

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?