Skip to main content
Glama

Delegum

by com.delegum

calcular_tarifa_freelance

Read-only

Calcula la tarifa que debería cobrar un freelance o autónomo (€/hora, €/día, €/semana) para alcanzar el ingreso neto que desea. Parte del neto objetivo, suma gastos, aplica IRPF, IVA y margen, y ajusta por los días realmente facturables (descontando fines de semana, vacaciones, festivos, bajas y % de ocupación). Devuelve tarifas con y sin IVA y la proyección anual.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipo_ivaNoTipo de IVA de tus facturas en %. Por defecto 21 (0 si estás exento).
tipo_irpfNoTipo de IRPF estimado en %. Por defecto 21.
dias_festivosNoDías festivos al año. Por defecto 14.
dias_enfermedadNoDías de baja previstos al año. Por defecto 5.
dias_vacacionesNoDías de vacaciones al año. Por defecto 22.
horas_semanalesNoHoras de trabajo por semana. Por defecto 40.
gastos_mensualesNoTotal de gastos mensuales deducibles en euros (cuota de autónomo, seguros, software, oficina, gestoría...).
margen_beneficioNoMargen de beneficio adicional sobre costes en %. Por defecto 15.
ingreso_neto_mensualYesIngreso neto mensual deseado en euros (lo que quieres llevarte a casa)
porcentaje_ocupacionNo% de días laborables que realmente se facturan (el resto es captación, admin, formación). Por defecto 70.

TDQS

A4.3/5.0
Behavior5/5

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

The description details the calculation steps: starting from net income, adding expenses, applying IRPF, IVA, margin, and adjusting for billable days. This goes well beyond annotations (readOnlyHint), adding rich behavioral context.

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?

The description is a single paragraph of three sentences, front-loaded with the main action, and every sentence adds value. No wasted words.

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 10 parameters (1 required) and no output schema, the description explains all inputs, the calculation logic, and the output (rates with/without IVA, annual projection). Sufficient for correct use.

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 coverage is 100% (each parameter has a description). The tool description adds no new per-parameter details but explains the overall calculation flow. Baseline 3 is appropriate.

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 clearly states the tool calculates freelance rates (€/hour, day, week) to achieve desired net income. It distinguishes from sibling calculators by specializing in freelance rate setting.

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 implies usage when a freelancer needs to determine their billing rate, but does not explicitly exclude alternative tools or provide when-not-to-use guidance. Context signals show many sibling calculators, so clear differentiation exists.

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

All Delegum 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
Disambiguation3/5

There are many tools with overlapping domains (e.g., multiple retirement calculators, home buying calculators), but detailed descriptions and explicit guidance on when to use comprehensive vs. specific tools help clarify. However, the sheer number (49) still creates potential confusion for an agent.

Naming Consistency5/5

All tools follow a consistent convention: infinitive verb or noun prefix (calcular, comparar, consulta) followed by descriptive noun phrase in snake_case. No mixed styles or irregularities.

Tool Count3/5

49 tools is high but justifiable given the broad scope of Spanish financial/legal calculations. It leans toward the heavy side but remains within a manageable range for a comprehensive server.

Completeness4/5

The tool set covers a wide spectrum of personal finance: income, taxes, housing, inheritance, self-employment, investments, etc. Only minor gaps exist (e.g., no separate tool for rental income beyond the alquiler tools, but included in IRPF).

Resources