Skip to main content
Glama

Xearno Tools

by tools.xearno

Steady Paycheck (Variable Income)

steady_paycheck
Read-only

Turn an up-and-down income into a safe monthly salary and a right-sized buffer. For freelancers, tipped workers, sellers, and seasonal earners: paste your last months of income and get the salary you can safely pay yourself, how big a buffer your actual swings require, and which months were spikes to bank rather than spend. The pay-yourself-a-salary method every advisor teaches by hand, as a calculator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bufferNoCash buffer today What’s in the account that smooths the gaps. Leave 0 if none yet.
incomesNoMonthly income, most recent months Comma-separated, 3–24 months, any order. More months = a truer picture.
essentialsNoEssential monthly costs Rent, food, utilities, insurance, minimum debt payments — the must-pays.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate the tool is read-only and deterministic. The description adds the behavioral context that it is a calculator using the 'pay-yourself-a-salary method', and explains what outputs are produced (salary, buffer, spike months). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two front-loaded sentences that efficiently convey the tool's purpose and usage. While it uses some evocative language, every part contributes meaning and there is no redundancy.

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?

Despite lacking an output schema, the description fully explains the return values: safe salary, required buffer, and spike months. Parameters are well-documented in both schema and description. The tool is complete for an AI agent's invocation.

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?

All three parameters have schema descriptions (100% coverage), but the tool description adds context by explaining the purpose of each parameter in the overall calculation (e.g., 'buffer: Cash buffer today', 'Leave 0 if none yet'). This slightly exceeds baseline.

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 transforms variable income into a safe monthly salary and buffer, targeting freelancers and similar earners. It specifies the verb 'turn' and the resource 'variable income', and distinguishes it from sibling financial calculators by focusing on income smoothing.

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 explicitly advises when to use ('for freelancers, tipped workers, sellers, and seasonal earners') and what data to provide ('paste your last months of income'). However, it does not explicitly state when not to use or mention alternative tools.

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

All Xearno Tools 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.9/5.0
Disambiguation4/5

Each tool targets a distinct niche (e.g., specific country tax rules, loan types, or legal calculations), with detailed descriptions that clarify boundaries. However, the large number of tools (66) could cause some confusion for an agent trying to select the right one for a general query, especially when multiple tools relate to the same country.

Naming Consistency4/5

Tool names follow a mostly predictable pattern: lowercase words separated by underscores, often starting with a country name (e.g., 'uk_stamp_duty_sdlt') or a topic (e.g., 'compound_growth'). There are minor deviations, such as abbreviations ('npv_irr', 'sip') and varying use of verbs, but overall the naming is clear and consistent.

Tool Count3/5

At 66 tools, the server is unusually large and covers an extensive range of financial and legal calculators. While each tool justifies its existence, the count exceeds the typical well-scoped range (3–15), making the server feel bloated. A more modular design might improve coherence.

Completeness4/5

The tool set covers a wide array of domains: personal income taxes, property taxes, loan calculations, investment returns, and specific country regulations. Minor gaps exist (e.g., missing tools for corporate taxes, general retirement planning, or insurance), but the overall coverage is thorough and addresses many niche scenarios that general AI handles poorly.

Resources