Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_concrete_volume_solver

Calculates concrete volume for slabs, footings, and cylindrical columns, including waste buffer, and estimates 60-lb and 80-lb premix bag counts.

Instructions

Concrete Volume & Premix Bag Yield Calculator: Calculates concrete volume in cubic yards and cubic meters for rectangular slabs, footings, and cylindrical columns with a standard 10% waste buffer and premix 60-lb and 80-lb bag counts.

GOVERNING MATHEMATICAL EQUATIONS:

  • Slab Volume: V_slab = [Length(ft) · Width(ft) · (Depth(in) / 12)] / 27 yd³

  • Column/Cylinder Volume: V_cyl = [π · (Diameter(ft)/2)² · Depth(ft)] / 27 yd³

  • Volume with Waste: V_total = V · (1 + Waste%/100)

  • Premix 80-lb Bag Yield: V_cuft / 0.60 cu ft/bag

  • Premix 60-lb Bag Yield: V_cuft / 0.45 cu ft/bag

USAGE GUIDELINES:

  • WHEN TO USE: Invoke to calculate concrete quantities for flatwork (driveways, patios, garage slabs), trench footings, and round sonotube piers before ordering ready-mix truck delivery or buying bagged premix concrete.

  • WHEN NOT TO USE: Do not use for dry-stack block fill or masonry mortar.

  • SIBLING DIFFERENTIATION: Dedicated strictly to structural cast-in-place concrete volume and commercial bag yield estimation. For rebar reinforcement grid sizing inside the concrete, query slug 'rebar-calculator' via 'omni_universal_query'. For driveway gravel base or sub-base compaction, query slug 'gravel-driveway' via 'omni_universal_query'. For paver joint sand, query slug 'polymeric-sand' via 'omni_universal_query'.

PARAMETER RELATIONSHIPS & CONSTRAINTS:

  • 'length_ft': Length of slab or footing in feet (min 1, max 500, default 20).

  • 'width_ft': Width of slab or footing in feet (min 1, max 500, default 10).

  • 'depth_in': Thickness or depth in inches (min 1, max 120, default 4). Converted internally to feet (depth / 12).

  • 'waste_pct': Percentage waste contingency buffer for spillage and subgrade unevenness (min 0, max 30, default 10).

BEHAVIOR, SAFETY & DETERMINISM:

  • Pure deterministic geometric volume calculation with IEEE 754 precision.

  • Read-only, idempotent, and stateless.

RETURN VALUE SCHEMA & QUANTITIES:

  • source (string): Canonical documentation URL (https://omnioperand.com/construction/concrete-volume/)

  • inputs (object): Echoed input dimensions and waste buffer

  • metrics (object): Calculated material metrics:

    • volume_cubic_yards_exact (number): Net volumetric displacement without buffer in cubic yards

    • volume_cubic_yards_with_waste (number): Total recommended order volume including waste buffer in cubic yards

    • volume_cubic_meters (number): Total metric volume including waste buffer in cubic meters

    • premix_80lb_bags_needed (number): Number of 80-lb commercial premix concrete bags required

    • premix_60lb_bags_needed (number): Number of 60-lb commercial premix concrete bags required

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

Input Schema

NameRequiredDescriptionDefault
depth_inNoThickness or depth of concrete in inches (e.g. 4 in for sidewalk/patio, 6 in for driveway).
width_ftNoWidth of concrete slab or footing in feet.
length_ftNoLength of concrete slab or footing in feet.
waste_pctNoWaste contingency buffer percentage (default 10%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

Annotations are empty, so the description carries the full burden and does well: it declares pure deterministic geometric calculation, IEEE 754 precision, read-only/idempotent/stateless behavior, and the exact equations used. It also documents the default 10% waste buffer and what it accounts for (spillage, subgrade unevenness). The only thing not covered is any error/precision caveat or rounding behavior on bag counts.

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?

Well-structured with labeled sections (equations, usage, parameters, behavior, return values) and front-loaded purpose, so an agent can skim to the relevant block. The equation list and the restatement of schema min/max/defaults are somewhat verbose for a 4-parameter tool, but each section is purposeful and nothing is filler prose.

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 stateless calculator with no output schema, the description lists every return field (volume in yd³ exact and with waste, m³, 60-lb and 80-lb bag counts) plus a documentation URL, so an agent knows exactly what comes back. Only minor gaps remain, such as whether bag counts are rounded up or fractional.

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 already 100%, so the baseline is 3; the description adds real meaning beyond the schema by explaining internal unit conversion ('depth / 12' to feet) and the physical purpose of waste_pct. It does repeat the min/max/default values already present in the schema, which limits it to a 4 rather than a 5.

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 ('Calculates concrete volume in cubic yards and cubic meters') and names the exact shapes covered (rectangular slabs, footings, cylindrical columns) plus bag yields. It explicitly scopes itself against named sibling slugs (rebar-calculator, gravel-driveway, polymeric-sand), so the agent can tell it apart without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit WHEN TO USE (flatwork, trench footings, sonotube piers, before ordering ready-mix or premix bags) and WHEN NOT TO USE (dry-stack block fill, masonry mortar), plus routing to alternatives via 'omni_universal_query' with concrete slugs. Both inclusion and exclusion conditions are stated, which is the top of the scale.

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