Bidalto: Spanish public tenders

Calcular oferta y margen

estimate_offer

Read-onlyIdempotent

Calcula el importe de una oferta a partir del presupuesto base sin IVA y la baja (%), y, si se indica el coste estimado, el margen en euros y en porcentaje, tanto sobre el precio de la oferta como sobre el coste (etiquetados por separado). Misma fórmula que el comprobador de bidalto.com. Acepta el id de una licitación para tomar su presupuesto base.

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": {
      "descuento": "<descuento>"
    },
    "name": "estimate_offer"
  }
}

Input Schema

Name	Required	Description
`id`	No	Id de la licitación (opcional): usa su presupuesto base si no se da precio.
`coste`	No	Coste estimado de ejecutar el contrato, en euros sin IVA (opcional).
`precio`	No	Presupuesto base de licitación sin IVA, en euros. Opcional si se da id.
`descuento`	Yes	Baja ofertada en % sobre el presupuesto base (0-90), p. ej. 12 para un 12 %.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds real context: that the tool may read a tender's base budget via id, that the formula matches bidalto.com's checker, and that the two margin ratios are reported separately and labeled.

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?

One front-loaded sentence covering inputs, conditional outputs, and the id fallback, with no padding. It is dense and nests several clauses, and the bidalto.com reference is of marginal value, but nothing is redundant.

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 carries the burden of describing return values and does so (offer amount, margin in euros, two percentage margins). Minor gaps remain, such as rounding or how conflicting id+precio inputs are resolved, but the calling agent has enough to act correctly.

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 baseline is 3. The description goes beyond it by explaining what coste triggers (margin outputs) and how id substitutes for precio, giving an agent the conditional logic the schema only hints at.

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 and computed outputs: offer amount from base budget minus a percentage discount, plus margin in euros and percent when a cost is supplied. This clearly separates it from the retrieval siblings get_tender and search_tenders, which do not compute anything.

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?

It explains the input condition (id can supply the base budget when precio is not given) but never states when an agent should call this versus looking up the tender first, and gives no exclusions or limits beyond the schema's 0-90 range.

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

All Bidalto: Spanish public tenders tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?