Skip to main content
Glama

WeGravel

Get Prices

get_prices
Read-onlyIdempotent

Get the delivered price of one material, for one quantity, at one US ZIP code. Only Florida ZIP codes are served; other ZIPs return an error. total is the full price in USD with delivery included; nothing is added to it. fullLoad is the price of one full truck load, the lowest price per unit. notes are facts about this order: the minimum order, how the price compares with a full load, and whether WeGravel prices the job by hand. quoteUrl opens the WeGravel quote form with the material, ZIP, and quantity filled in. pageUrl is the WeGravel page for this material in the delivery city (null when there is no page).

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>",
      "quantity": "<quantity>",
      "zip": "<zip>"
    },
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code of the delivery address. Florida only.
unitNoUnit of `quantity`: "yd3" (cubic yards) or "ton". Default: the unit the material sells by (see list_materials).
materialYesMaterial slug from list_materials (a material name also works).
quantityYesQuantity to deliver, in `unit`. Must be greater than 0.

Output Schema

NameRequiredDescriptionDefault
unitYes
notesYes
totalYes
pageUrlYes
currencyYes
fullLoadYes
materialYes
quantityYes
quoteUrlYes
unitPriceYes
truckLoadsYes
destinationYes
needsCustomQuoteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real meaning: 'total' includes delivery with nothing added, 'fullLoad' is the lowest per-unit price, and 'pageUrl' can be null. That clarifies pricing semantics that a schema alone would not convey.

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-loads the purpose, then the geographic constraint, then the output semantics, with no filler sentences. The field-by-field enumeration is dense but each clause carries information an agent would otherwise have to guess.

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 need not be spelled out, yet the description still explains the pricing fields and the null case for pageUrl. Combined with the Florida-only error behavior, an agent has enough to call this correctly; only the relationship to compare_prices is left implicit.

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%, including the Florida-only ZIP note and the unit default tied to list_materials, so the schema already does the parameter work. The description adds only a restatement of material/quantity/zip scope and no extra syntax or format detail, making the baseline 3 correct.

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 with explicit scope: 'the delivered price of one material, for one quantity, at one US ZIP code.' The 'one material / one quantity / one ZIP' framing implicitly separates it from the sibling compare_prices, which the agent can reason about without opening either schema.

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 a clear when-not condition: only Florida ZIPs are served and other ZIPs return an error, which prevents a whole class of failed calls. It stops short of naming alternatives such as compare_prices for multi-material lookups, so it lacks the explicit routing that would earn a 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