Skip to main content
Glama

Meteoro Minerals

Prediseño de mezcla de concreto / Concrete mix pre-design

prediseno_mezcla
Idempotent

Use when the user asks for reference quantities per m³ of non-air-entrained concrete with Meteoro Guayuriba aggregates (ACI 211.1, f'c from 17 to 31.7 MPa (f'cr up to 40 MPa, the maximum of the w/c ratio table)), such as how much cement a 3,000 psi concrete takes: returns the quantities with the exact table sources and a verifiable folio, never prices; it registers a folio with no personal data. / Úsela cuando el usuario pregunte cantidades por m³ de un concreto con agregados Meteoro Guayuriba (f'c de 17 a 31,7 MPa (f'cr hasta 40 MPa, el máximo de la tabla de relación a/c)), por ejemplo cuánto cemento lleva un concreto de 3.000 psi; registra un folio sin datos personales.

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": {
      "fc": "<fc>",
      "asentamiento": "<asentamiento>",
      "grava": "<grava>"
    },
    "name": "prediseno_mezcla"
  }
}

Input Schema

NameRequiredDescriptionDefault
fcYesResistencia especificada f'c: número en MPa (21) o psi (3000), o texto con su unidad ("21 MPa", "3000 psi", "210 kg/cm2"). / Specified strength f'c: a number in MPa or psi, or one string with its unit. Alias: resistencia, fc_mpa.
langNoIdioma de la respuesta; si se omite, se usa el idioma de la consulta. / Answer language; defaults to the language of the query. Alias: idioma, language, locale.
gravaYesGrava Meteoro Guayuriba: 1" (acepta "1", "1 pulgada", "1 in", "25", "25 mm") o 1/2" (acepta "1/2", "0.5", "media", "12.5", "12,5 mm"). / Meteoro Guayuriba gravel: 1" or 1/2", with or without the inch mark, or in mm. Alias: tamano_maximo, tamaño_maximo.
ac_maximaNoOpcional: relación a/c máxima por durabilidad que define el ingeniero responsable (NSR-10 C.4), de 0.35 a 0.7; si es menor que la a/c por resistencia, rige y el cemento se recalcula. / Optional maximum w/c ratio for durability set by the responsible engineer, 0.35 to 0.7; when lower than the w/c from strength it governs. Alias: a_c_max, wc_max.
fc_unidadNoUnidad de f'c: MPa (por defecto), psi o kg/cm2; sin unidad, valores mayores que 100 se leen como psi. / Unit of f'c: MPa (default), psi or kg/cm2. Alias: unidad.
asentamientoYesAsentamiento: 25-50, 75-100 o 150-175 mm. Acepta "75-100", "75 a 100", "3-4 pulgadas", "4 in" o un valor como 100 (mm). / Slump: 25-50, 75-100 or 150-175 mm; accepts ranges, inches or a single value in mm. Alias: slump, asentamiento_mm.
humedad_arenaNoHumedad de la arena en %. / Sand moisture %.
humedad_gravaNoHumedad de la grava en %, para corregir agua. / Gravel moisture %.
densidad_cementoNoDensidad del cemento en g/cm³; por defecto la del motor. / Cement density in g/cm³.

Output Schema

NameRequiredDescriptionDefault
citaYesUna oración para citar textualmente, respaldada por fuente / One sentence to quote verbatim, backed by fuente
hashNo
folioNo
motorNo
notasNo
fuenteYesPágina canónica de www.meteoro.io que respalda la respuesta / Canonical source page
idiomaYes
metodoNo
paginaNo
mensajeNo
whatsappYes
verificarNo
actualizadoYesFecha de actualización de los datos (ISO) / Data update date
fuera_de_alcanceNo
valores_de_tablaNo
aviso_obligatorioNo
cantidades_por_m3No
ignored_argumentsNoArgumentos recibidos que no se usaron (desconocidos o reemplazados por el nombre canónico) / Received arguments that were not used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations mark the tool as not read-only, and the description explains why: it registers a folio with no personal data, which is exactly the side effect annotations flag but cannot explain. It also discloses that results carry table sources and a verifiable folio. It says nothing about idempotency, failure modes, or rate limits, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The triggering condition is correctly front-loaded, but the body is a dense single sentence with nested parentheses ("(f'cr up to 40 MPa, the maximum of the w/c ratio table)") that is hard to parse. The full bilingual duplication doubles length for content that is otherwise overlapping.

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?

An output schema exists, so return values are covered elsewhere; the description still notes quantities come with table sources and a folio. Combined with the strength bounds and the folio side effect, an agent has enough to decide when and how to call it.

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 the heavy lifting is already done. The description adds only the f'c domain (17–31.7 MPa, f'cr up to 40 MPa) and the psi/kg-cm² example, without explaining the optional humidity, density, or ac_maxima parameters beyond what the schema says.

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 resource: returns reference quantities per m³ of non-air-entrained concrete for Meteoro Guayuriba aggregates under ACI 211.1, with a bounded strength range. It also explicitly excludes pricing, which separates it from siblings such as precios_referencia.

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?

'Use when the user asks for...' plus a concrete example (how much cement a 3,000 psi mix takes) gives a clear trigger. The 'never prices' clause implicitly routes price questions elsewhere but no sibling is named, so the alternative path is only implied.

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