Skip to main content
Glama

Delegum

by com.delegum

comparar_autonomo_vs_sl

Read-only

Compara la carga fiscal total (Seguridad Social + IRPF/IS + dividendos) de operar como autónomo persona física frente a constituir una Sociedad Limitada (SL). Indica cuál conviene y el umbral.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipo_isNoTipo de IS para la SL. Por defecto "general".
beneficio_anualYesBeneficio bruto anual de la actividad en euros
gastos_deduciblesNoGastos deducibles anuales. Por defecto 0.
repartir_dividendosNoSi la SL reparte dividendos al socio. Por defecto true.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, making safety clear. The description adds the comparison details but does not disclose assumptions, data freshness, or limitations (e.g., based on current tax laws).

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?

Two short sentences front-load the purpose and output. No extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of tax comparison, the description adequately explains what the tool does and its output. However, it could mention that the calculation is based on current tax rules or note the output format. Still sufficient for an agent.

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%; the description does not add meaning beyond what the schema provides for each parameter. Baseline 3 is appropriate as the schema is self-sufficient.

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 compares fiscal load (Social Security + IRPF/IS + dividends) between being self-employed and forming a SL, and indicates which is better and the threshold. This distinguishes it from other comparison tools like comparar_donacion_vs_herencia.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when deciding between self-employment and SL, and mentions the output (which is better and threshold), but does not explicitly state when to use this tool over alternatives or provide exclusions or prerequisites.

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