Skip to main content
Glama

Herramientas de Ecuador · ADVISE.ia

Calcular los días de cartera (DSO)

calcular_dias_de_cartera
Read-onlyIdempotent

Calcula los días de cartera o período medio de cobro (DSO) de una empresa: (cuentas por cobrar comerciales ÷ ventas a crédito del período) × días del período, con las ventas a crédito por día, la rotación de cartera, el atraso promedio frente al plazo de crédito, la caja que se libera si los clientes pagan en el plazo y la caja que se libera al bajar cierto número de días. Úsala cuando pregunten por el DSO, los días de cobro o cuánto dinero se libera cobrando más rápido. Solo usa las cifras que se le dan, sin promedios de industria.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cuentas_por_cobrar": "<cuentas_por_cobrar>",
      "ventas_credito": "<ventas_credito>"
    },
    "name": "calcular_dias_de_cartera"
  }
}

Input Schema

NameRequiredDescriptionDefault
dias_a_bajarNoDías de cartera que se quiere bajar, para calcular la caja que se libera (opcional).
dias_periodoNoDías del período de las ventas: 365 (un año, por defecto), 90 (trimestre), 30 (mes) u otro.
ventas_creditoYesVentas a crédito del período, en USD (sin ventas al contado; mismo criterio de IVA que el saldo por cobrar).
cuentas_por_cobrarYesCuentas por cobrar comerciales al cierre del período, en USD (solo cartera de clientes de corto plazo).
plazo_credito_diasNoPlazo de crédito promedio pactado con los clientes, en días (opcional; sirve para el atraso promedio).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: it enumerates the derived outputs (rotación, atraso promedio, caja liberada) and imposes an input discipline — "Solo usa las cifras que se le dan, sin promedios de industria" — which tells the agent not to benchmark.

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 definition is front-loaded with the formula and then the usage trigger, with no filler sentences. The first sentence is dense and long, but every clause carries information an agent needs.

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?

With no output schema, the description correctly compensates by enumerating the return values (ventas a crédito por día, rotación, atraso, caja liberada en el plazo y al bajar días). For a five-parameter read-only calculator this is essentially complete, with only default/edge behavior for dias_periodo left to the schema.

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?

Schema coverage is 100%, so the baseline would be 3, but the description links parameters to results rather than merely restating them: dias_a_bajar produces the released-cash figure and plazo_credito_dias produces the average delay versus the credit term. That mapping helps an agent decide which optional parameters actually matter for a given question.

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?

States a specific verb ("Calcula") and resource ("días de cartera o período medio de cobro (DSO)"), and goes further by giving the exact formula, which leaves no ambiguity about what the tool returns. The topic is clearly distinct from the labor/tax calculators among its siblings, so an agent can select it without opening the schema.

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?

"Úsela cuando pregunten por el DSO, los días de cobro o cuánto dinero se libera cobrando más rápido" gives explicit trigger phrasing for invocation. It lacks any when-not or alternative-tool steering, but the domain is narrow enough that no ambiguity is likely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources