Skip to main content
Glama

bonificaciones

Retrieves long-term contract bonuses and compensation thresholds for guaranteed fuel quantities, filtered by product name (e.g., kerosene, gasoline).

Instructions

Bonificaciones y compensaciones de los contratos a largo plazo (PDF de Exolum).

Por cumplir (bonificación) o incumplir (compensación) las cantidades garantizadas. Hay un documento por familia de productos; aplica_a dice a qué productos e instalaciones corresponde. producto: filtra por parte del nombre («queroseno», «gasolinas»). Incluye los umbrales en % y las notas del documento.

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": "bonificaciones"
  }
}

Input Schema

NameRequiredDescriptionDefault
productoNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does carry some of the burden: it discloses the source (Exolum PDFs), the granularity (one document per product family), and that thresholds in % and document notes are returned. It does not state read-only nature, error behavior, or result shape, though an output schema is present to cover returns.

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?

Front-loaded with the resource and source, followed by the semantic distinction, the document granularity, and the filter behavior — each sentence adds information. Slightly dense but no filler.

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?

For a single-optional-parameter lookup tool with an output schema, the description covers what the data is, where it comes from, how it is partitioned, how to filter, and what fields (thresholds, notes) to expect. Only the absence of explicit sibling routing keeps it from a 5.

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 0%, so the description must compensate, and it does: it explains that `producto` filters by *part* of the name (partial match, not exact), with concrete examples («queroseno», «gasolinas») and a default of null. That substring-matching semantics is genuinely beyond what the bare string schema conveys.

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?

It names a specific resource — long-term contract bonuses and compensations sourced from Exolum PDFs — and disambiguates the two terms (bonificación = meeting guaranteed quantities, compensación = missing them). It does not explicitly contrast with any sibling, but the domain is distinct enough that an agent can tell it apart from tools like buscar_precios or capacidades.

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?

Usage is only implied: an agent infers you call this to look up bonus/compensation thresholds tied to product families. There is no explicit when-to-use vs when-not statement and no alternative tool is named (e.g., when to prefer buscar_precios for pricing instead).

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