Skip to main content
Glama

Calculadora de rentabilidad real

ml_rentabilidad
Read-only

Calculate real net profit and margin per product on MercadoLibre Colombia by subtracting commission, Product Ads spend, taxes, shipping, and cost; requests missing cost/tax data and shows supported ACOS.

Instructions

El desglose real peso por peso de un producto: precio de venta MENOS comisión de MercadoLibre (tarifa real del tipo de publicación) MENOS publicidad por unidad (gasto de Product Ads en vivo del período) MENOS impuestos MENOS costo de envío MENOS costo del producto = ganancia neta y margen. Pide lo que falta (costo e impuestos NUNCA se inventan) y dice hasta qué ACOS aguanta el producto.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ml_rentabilidad"
  }
}

Input Schema

NameRequiredDescriptionDefault
costoNoCosto del producto (lo que te sale a vos) — SIEMPRE preguntarlo al usuario
cuentaNouser_id de la cuenta de ML si hay varias conectadas (ver ml_cuentas)
precioNoPrecio de venta; si hay item_id se toma el de la publicación
item_idNoSi se indica, trae precio, tipo de publicación y gasto de ads reales
dias_adsNoPeríodo para promediar la publicidad (default 30)
costo_envioNoLo que paga el vendedor de envío por unidad (si ofrece envío gratis). Default 0
impuestos_pctNo% de impuestos sobre el precio (IVA 19% + ICA según municipio, para régimen común) — SIEMPRE preguntarlo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0-tyl.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context: it discloses that it will prompt for missing inputs, that cost and taxes are never fabricated, and that it reports the maximum ACOS a product can bear — useful traits beyond the annotation.

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 formula is front-loaded in one sentence and the behavioral caveat follows, with zero filler. It is dense and heavy on all-caps emphasis, but every clause maps to a distinct part of the calculation or behavior.

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 does explain the return values (net profit, margin, tolerable ACOS). Combined with 100% parameter documentation and a readOnly annotation, an agent has enough to call it correctly; the only gap is the absence of sibling comparisons.

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 is already documented in the schema, including the 'SIEMPRE preguntarlo' notes for costo and impuestos_pct. The description reinforces that item_id pulls live price and ads spend but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource: breaks down peso-by-peso profitability of a product, with the exact formula chain (price minus commission, ads, taxes, shipping, cost = net profit and margin). This is clearly distinguishable from siblings like ml_comisiones or ml_precio_catalogo, which cover only a piece of the calculation.

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?

Implies usage context (per-unit profitability of a product, with item_id pulling real price/publication type/ads) and warns that missing cost and taxes must be asked, never invented. However, it never states when to prefer this over ml_comisiones, ml_metricas, or ml_panel_ventas, so sibling routing is left to inference.

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