Skip to main content
Glama

WeGravel

Calculate Quantity

calculate_quantity
Read-onlyIdempotent

Calculate how much material a rectangular area needs. Give the length and width in feet and the depth in inches. The result gives cubic yards and tons, and orderQuantity in the unit WeGravel sells the material by, with a safety margin and the minimum order included. Pass orderQuantity and unit to get_prices to get the price and the quote link.

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": {
      "material": "<material>",
      "lengthFt": "<lengthFt>",
      "widthFt": "<widthFt>",
      "depthInches": "<depthInches>"
    },
    "name": "calculate_quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthFtYesWidth of the area, in feet.
lengthFtYesLength of the area, in feet.
materialYesMaterial slug from list_materials (a material name also works).
depthInchesYesDepth of the material, in inches.

Output Schema

NameRequiredDescriptionDefault
tonsYes
unitYes
areaSqFtYes
materialYes
cubicYardsYes
truckLoadsYes
depthInchesYes
orderQuantityYes
safetyMarginPercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent operation, so the description needn't re-litigate safety. It adds real behavioral context beyond annotations by disclosing that the returned `orderQuantity` already includes a safety margin and the minimum order, which materially affects how the agent should interpret and pass the result onward.

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

Conciseness5/5

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

Four sentences arranged as purpose, inputs, output contents, and next step — front-loaded with zero filler. Every sentence carries distinct actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and 100% parameter coverage, the description only needs to explain intent, units, and workflow, and it does all three. The agent knows exactly what to supply, what it receives, and where to send the result next.

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 coverage is 100%, so all four parameters are already documented in the schema, including that `material` accepts a name as well as a slug. The description restates the feet/inch units but adds no format or edge-case meaning beyond what the schema provides, which is the baseline-3 situation.

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 ('Calculate how much material a rectangular area needs') plus the input units and the geometry it supports. An agent can immediately tell this is the quantity/volume estimator, distinct from get_prices, compare_prices, and list_materials.

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?

Gives clear sequencing: compute here first, then 'Pass `orderQuantity` and `unit` to get_prices to get the price and the quote link.' That is explicit routing to the correct sibling. It stops short of stating when-not-to-use cases (e.g., non-rectangular areas), so it is not a full 5.

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