Skip to main content
Glama

WeGravel

Compare Prices

compare_prices
Read-onlyIdempotent

Compare the delivered price of several materials at one Florida ZIP code, cheapest first. Each row is the price of one full truck load, in USD with delivery included, in the unit the material sells by. An entry of materials can be a slug, a name, or a word that names a group ("mulch", "sand", "crushed stone"): a group word adds every material that matches it. At most 12 materials are priced in one call; notPriced lists the rest with the reason. Use get_prices for the price of an exact quantity.

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": {
      "materials": "<materials>",
      "zip": "<zip>"
    },
    "name": "compare_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code of the delivery address. Florida only.
materialsYesMaterial slugs, names, or group words such as "mulch".

Output Schema

NameRequiredDescriptionDefault
pricesYes
currencyYes
notPricedYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, yet the description still adds substantial behavior: per-row pricing is one full truck load in USD with delivery included, in the material's selling unit, and the 12-material cap produces a partial result with a `notPriced` list of reasons. That partial-success disclosure is exactly the kind of thing annotations cannot convey.

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 tight sentences, front-loaded with purpose and ordering, then pricing semantics, then the expansion rule and cap, then the alternative. No filler and no repetition of what the schema already says.

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?

An output schema exists so return values need not be restated, and the description still covers the two things an agent most needs to interpret results: what a row represents (one full truck load, delivered) and what happens on overflow (`notPriced` with reasons). Nothing needed to call it correctly is missing.

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 100%, so the baseline is 3, but the description goes further by explaining that a `materials` entry may be a slug, a name, or a group word, and that a group word adds every matching material. That expansion rule is not in the schema's own parameter text and materially changes how an agent should populate the array.

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 ('Compare the delivered price of several materials'), plus the scope ('at one Florida ZIP code') and the ordering guarantee ('cheapest first'). The agent can immediately distinguish this from get_prices (exact quantity) and list_materials without opening a 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?

Explicitly routes exact-quantity pricing to get_prices, and explains that group words expand to all matching materials, which is a usage-level decision the agent must make. It stops short of a fuller when-not-to-use statement (e.g. non-Florida addresses, or when a single material is wanted), so it is clear but not exhaustive.

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